CVE-2026-64025 bpf, skmsg: fix verdict sk_data_ready racing with ktls rx

In the Linux kernel, the following vulnerability has been resolved: bpf, skmsg: fix verdict skdataready racing with ktls rx skpsockstrpdataready already checks tlsswhasctxrx and defers to psock-saveddataready when a TLS RX context is present, avoiding a conflict with the TLS strparser's ownership...

EUVD-2026-45562

In the Linux kernel, the following vulnerability has been resolved: bridge: Fix sleep in atomic context in netlink path Since the introduction of the netlink configuration path for bridge ports in commit 25c71c75ac87 "bridge: bridge port parameters over netlink", brsetport was always called with...

CVE-2026-63989

The Linux kernel contains a vulnerability where the br_setport() function could be called with the bridge lock held while processing attributes that do not require it, such as bridge flags, FDB port flushing, and multicast attributes. This led to the execution of dev_set_promiscuity() in an atomi...

CVE-2026-63989

In the Linux kernel, the following vulnerability has been resolved: bridge: Fix sleep in atomic context in netlink path Since the introduction of the netlink configuration path for bridge ports in commit 25c71c75ac87 "bridge: bridge port parameters over netlink", brsetport was always called with...

EUVD-2026-45561

In the Linux kernel, the following vulnerability has been resolved: bridge: Fix sleep in atomic context in sysfs path Since the start of the git history, brportstore always acquired the bridge lock. Back then this decision made sense: The bridge lock protects the STP state of the bridge and its...

CVE-2026-63988 bridge: Fix sleep in atomic context in sysfs path

In the Linux kernel, the following vulnerability has been resolved: bridge: Fix sleep in atomic context in sysfs path Since the start of the git history, brportstore always acquired the bridge lock. Back then this decision made sense: The bridge lock protects the STP state of the bridge and its...

CVE-2026-63988

A vulnerability exists in the Linux kernel bridge subsystem where the brport_store() function incorrectly acquired the bridge lock while processing several attributes that do not require it, such as Bridge flags , FDB port flushing , Multicast attributes , Group forward mask , and Backup port . B...

CVE-2026-63980 net/handshake: Use spin_lock_bh for hn_lock

In the Linux kernel, the following vulnerability has been resolved: net/handshake: Use spinlockbh for hnlock nvmettcpstatechange, a socket callback that runs in BH context, can reach handshakereqcancel via nvmettcpschedulereleasequeue and tlshandshakecancel. handshakereqcancel acquires hn-hnlock...

CVE-2026-63955

The CVE-2026-63955 entry concerns a Linux kernel issue in mm/vmalloc where __get_vm_area_node() would trigger BUG_ON(in_interrupt()) even when BH were disabled. The call path through __vlan_add()/br_fdb_add_local() and rhashtable_lookup_insert_fast() could reach kvmalloc/vmalloc, leading to a BUG...

CVE-2026-63955 mm/vmalloc: do not trigger BUG() on BH disabled context

In the Linux kernel, the following vulnerability has been resolved: mm/vmalloc: do not trigger BUG on BH disabled context getvmareanode currently triggers a BUG if ininterrupt returns true. However, ininterrupt also reports true when BH are disabled. The bridge code can call...

CVE-2026-63955

In the Linux kernel, the following vulnerability has been resolved: mm/vmalloc: do not trigger BUG on BH disabled context getvmareanode currently triggers a BUG if ininterrupt returns true. However, ininterrupt also reports true when BH are disabled. The bridge code can call...

CVE-2026-63955 mm/vmalloc: do not trigger BUG() on BH disabled context

In the Linux kernel, the following vulnerability has been resolved: mm/vmalloc: do not trigger BUG on BH disabled context getvmareanode currently triggers a BUG if ininterrupt returns true. However, ininterrupt also reports true when BH are disabled. The bridge code can call...

CVE-2026-63941 KVM: arm64: Correctly cap ZCR_EL2 provided by a guest hypervisor

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Correctly cap ZCREL2 provided by a guest hypervisor ZCREL2 can be updated by a VHE guest hypervisor either using ZCREL2 which traps or ZCREL1 which does not trap. KVM handles both in different way: - on ZCREL2 trap,...

MINI-24CM-V4F4-566W

Bulletin has no description...

CVE-2026-63805

In the Linux kernel, the following vulnerability has been resolved: crypto: nx - fix nxcryptoctxexit argument nxcryptoctxshashexit calls nxcryptoctxexit with cryptoshashctx... but cryptoshashctx gives a nxcryptoctx , not a cryptotfm . Fix the type in nxcryptoctxexit and drop the bogus cryptotfmct...

CVE-2026-63830

In the Linux kernel, the following vulnerability has been resolved: net: skmsg: preserve sg.copy across SG transforms The skmsg sg.copy bitmap is part of the scatterlist entry ownership state. A set bit tells skmsgcomputedatapointers not to expose the entry through writable BPF ctx-data. This...

CVE-2026-63805 crypto: nx - fix nx_crypto_ctx_exit argument

In the Linux kernel, the following vulnerability has been resolved: crypto: nx - fix nxcryptoctxexit argument nxcryptoctxshashexit calls nxcryptoctxexit with cryptoshashctx... but cryptoshashctx gives a nxcryptoctx , not a cryptotfm . Fix the type in nxcryptoctxexit and drop the bogus cryptotfmct...

EUVD-2026-45471

In the Linux kernel, the following vulnerability has been resolved: crypto: nx - fix nxcryptoctxexit argument nxcryptoctxshashexit calls nxcryptoctxexit with cryptoshashctx... but cryptoshashctx gives a nxcryptoctx , not a cryptotfm . Fix the type in nxcryptoctxexit and drop the bogus cryptotfmct...

CVE-2026-63805

CVE-2026-63805 concerns a Linux kernel crypto issue where nx_crypto_ctx_shash_exit calls nx_crypto_ctx_exit with a crypto_shash_ctx returning a nx_crypto_ctx* instead of a crypto_tfm*. This type mismatch triggers a kernel oops in AF_ALG usage (hashing path) and similarly affects nx_crypto_ctx_skc...

CVE-2026-63805

In the Linux kernel, the following vulnerability has been resolved: crypto: nx - fix nxcryptoctxexit argument nxcryptoctxshashexit calls nxcryptoctxexit with cryptoshashctx... but cryptoshashctx gives a nxcryptoctx , not a cryptotfm . Fix the type in nxcryptoctxexit and drop the bogus cryptotfmct...