UBUNTU-CVE-2024-39509

In the Linux kernel, the following vulnerability has been resolved: HID: core: remove unnecessary WARNON in implement Syzkaller hit a warning 1 in a call to implement when trying to write a value into a field of smaller size in an output report. Since implement already has a warn message printed...

CVE-2024-39509

In the Linux kernel, the following vulnerability has been resolved: HID: core: remove unnecessary WARNON in implement Syzkaller hit a warning 1 in a call to implement when trying to write a value into a field of smaller size in an output report. Since implement already has a warn message printed...

CVE-2024-40996

CVE-2024-40996 affects the Linux kernel. Problem: bpf: Avoid splat in pskb_pull_reason where a debug WARN may trigger for SYZKALLER-style nets; not interesting for valid traffic and can be suppressed. Root cause involves a debug hint in pskb_may_pull when CONFIG_DEBUG_NET=y; with CONFIG_DEBUG_NET...

CVE-2024-40988 drm/radeon: fix UBSAN warning in kv_dpm.c

In the Linux kernel, the following vulnerability has been resolved: drm/radeon: fix UBSAN warning in kvdpm.c Adds bounds check for sumovidmappingentry...

CVE-2024-40988 drm/radeon: fix UBSAN warning in kv_dpm.c

In the Linux kernel, the following vulnerability has been resolved: drm/radeon: fix UBSAN warning in kvdpm.c Adds bounds check for sumovidmappingentry...

CVE-2024-40988

CVE-2024-40988 affects the Linux kernel DRM/Radeon driver. The issue is a UBSAN warning caused by a missing bounds check in kv_dpm.c (sumo_vid_mapping_entry). The patch adds the necessary bounds check, resolving the UBSAN warning. The description indicates the change is a bounds validation fix ra...

CVE-2024-40988 drm/radeon: fix UBSAN warning in kv_dpm.c

In the Linux kernel, the following vulnerability has been resolved: drm/radeon: fix UBSAN warning in kvdpm.c Adds bounds check for sumovidmappingentry...

CVE-2024-40987 drm/amdgpu: fix UBSAN warning in kv_dpm.c

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix UBSAN warning in kvdpm.c Adds bounds check for sumovidmappingentry...

CVE-2024-40983 tipc: force a dst refcount before doing decryption

In the Linux kernel, the following vulnerability has been resolved: tipc: force a dst refcount before doing decryption As it says in commit 3bc07321ccc2 "xfrm: Force a dst refcount before entering the xfrm type handlers": "Crypto requests might return asynchronous. In this case we leave the rcu...

CVE-2024-40983 tipc: force a dst refcount before doing decryption

In the Linux kernel, the following vulnerability has been resolved: tipc: force a dst refcount before doing decryption As it says in commit 3bc07321ccc2 "xfrm: Force a dst refcount before entering the xfrm type handlers": "Crypto requests might return asynchronous. In this case we leave the rcu...

CVE-2024-40958 netns: Make get_net_ns() handle zero refcount net

In the Linux kernel, the following vulnerability has been resolved: netns: Make getnetns handle zero refcount net Syzkaller hit a warning: refcountt: addition on 0; use-after-free. WARNING: CPU: 3 PID: 7890 at lib/refcount.c:25 refcountwarnsaturate+0xdf/0x1d0 Modules linked in: CPU: 3 PID: 7890...

CVE-2024-40958

CVE-2024-40958 relates to the Linux kernel: get_net_ns() may perform a refcount increment on a net namespace with zero refcount, triggering a use-after-free warning and potential kernel panic. The root cause is an addition on 0 refcount via get_net_ns(), surfaced during operations like netns swit...

CVE-2024-40958 netns: Make get_net_ns() handle zero refcount net

In the Linux kernel, the following vulnerability has been resolved: netns: Make getnetns handle zero refcount net Syzkaller hit a warning: refcountt: addition on 0; use-after-free. WARNING: CPU: 3 PID: 7890 at lib/refcount.c:25 refcountwarnsaturate+0xdf/0x1d0 Modules linked in: CPU: 3 PID: 7890...

CVE-2024-40958 netns: Make get_net_ns() handle zero refcount net

In the Linux kernel, the following vulnerability has been resolved: netns: Make getnetns handle zero refcount net Syzkaller hit a warning: refcountt: addition on 0; use-after-free. WARNING: CPU: 3 PID: 7890 at lib/refcount.c:25 refcountwarnsaturate+0xdf/0x1d0 Modules linked in: CPU: 3 PID: 7890...

CVE-2024-40958

In the Linux kernel, the following vulnerability has been resolved: netns: Make getnetns handle zero refcount net Syzkaller hit a warning: refcountt: addition on 0; use-after-free. WARNING: CPU: 3 PID: 7890 at lib/refcount.c:25 refcountwarnsaturate+0xdf/0x1d0 Modules linked in: CPU: 3 PID: 7890...

CVE-2024-40950 mm: huge_memory: fix misused mapping_large_folio_support() for anon folios

In the Linux kernel, the following vulnerability has been resolved: mm: hugememory: fix misused mappinglargefoliosupport for anon folios When I did a large folios split test, a WARNING " 5059.122759 T166 Cannot split file folio to non-0 order" was triggered. But the test cases are only for anonmo...

CVE-2024-40922 io_uring/rsrc: don't lock while !TASK_RUNNING

In the Linux kernel, the following vulnerability has been resolved: iouring/rsrc: don't lock while !TASKRUNNING There is a report of iorsrcrefquiesce locking a mutex while not TASKRUNNING, which is due to forgetting restoring the state back after ioruntaskworksig and attempts to break out of the...

CVE-2024-40920 net: bridge: mst: fix suspicious rcu usage in br_mst_set_state

In the Linux kernel, the following vulnerability has been resolved: net: bridge: mst: fix suspicious rcu usage in brmstsetstate I converted brmstsetstate to RCU to avoid a vlan use-after-free but forgot to change the vlan group dereference helper. Switch to vlan group RCU deref helper to fix the...

CVE-2024-40920

CVE-2024-40920 affects the Linux kernel net: bridge: mst component. Root cause: br_mst_set_state was converted to RCU to avoid a VLAN use-after-free, but the vlan group dereference helper was not updated, triggering suspicious RCU usage. The fix switches to the vlan group RCU deref helper to addr...

CVE-2024-40917

CVE-2024-40917 affects the Linux kernel memory management (memblock) related to NUMA/node handling. The issue stems from memblock_validate_numa_coverage() allowing a NUMA_NO_NODE condition and memblock_alloc_range_nid() warning about MAX_NUMNODES, leading to a NULL dereference in memmap_init() wh...