https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-14T18:15:40.333249+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cve-2024-26996 CVE-2024-26996 — usb: gadget: f_ncm: Fix UAF ncm object at re-bind after usb ep transport error 2026-10-14T18:15:40.509544+00:00

Affected: Linux

In the Linux kernel, the following vulnerability has been resolved:

usb: gadget: f_ncm: Fix UAF ncm object at re-bind after usb ep transport error

When ncm function is working and then stop usb0 interface for link down, eth_stop() is called. At this piont, accidentally if usb transport error should happen in usb_ep_enable(), 'in_ep' and/or 'out_ep' may not be enabled.

After that, ncm_disable() is called to disable for ncm unbind but gether_disconnect() is never called since 'in_ep' is not enabled.

As the result, ncm object is released in ncm unbind but 'dev->port_usb' associated to 'ncm->port' is not NULL.

And when ncm bind again to recover netdev, ncm object is reallocated but usb0 interface is already associated to previous released ncm object.

Therefore, once usb0 interface is up and eth_start_xmit() is called, released ncm object is dereferrenced and it might cause use-after-free memory.

[function unlink via configfs] usb0: eth_stop dev->port_usb=ffffff9b179c3200 --> error happens in usb_ep_enable(). NCM: ncm_disable: ncm=ffffff9b179c3200 --> no gether_disconnect() since ncm->port.in_ep->enabled is false. NCM: ncm_unbind: ncm unbind ncm=ffffff9b179c3200 NCM: ncm_free: ncm free ncm=ffffff9b179c3200 <-- released ncm

[function link via configfs] NCM: ncm_alloc: ncm alloc ncm=ffffff9ac4f8a000 NCM: ncm_bind: ncm bind ncm=ffffff9ac4f8a000 NCM: ncm_set_alt: ncm=ffffff9ac4f8a000 alt=0 usb0: eth_open dev->port_usb=ffffff9b179c3200 <-- previous relea…

 https://cve.radiocsirt.org/vuln/usn-6893-1 USN-6893-1 — linux, linux-azure, linux-gcp, linux-ibm, linux-intel, linux-lowlatency, linux-oem-6.8, linux-raspi vulnerabilities 2026-10-14T18:15:40.509677+00:00

Affected: Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-azure, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-ibm, Ubuntu:24.04:LTS: linux-intel, Ubuntu:24.04:LTS: linux-lowlatency, Ubuntu:24.04:LTS: linux-oem-6.8, Ubuntu:24.04:LTS: linux-raspi

It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel when modifying certain settings values through debugfs. A privileged local attacker could use this to cause a denial of service. (CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems: - ARM64 architecture; - RISC-V architecture; - S390 architecture; - x86 architecture; - Block layer subsystem; - Compute Acceleration Framework; - Accessibility subsystem; - Android drivers; - Drivers core; - Bluetooth drivers; - Clock framework and drivers; - Data acquisition framework and drivers; - Cryptographic API; - Buffer Sharing and Synchronization framework; - GPU drivers; - On-Chip Interconnect management framework; - IOMMU subsystem; - Multiple devices driver; - Media drivers; - VMware VMCI Driver; - Network drivers; - Microsoft Azure Network Adapter (MANA) driver; - Device tree and open firmware driver; - Chrome hardware platform drivers; - i.MX PM domains; - TI SCI PM domains driver; - S/390 drivers; - SCSI drivers; - SPI subsystem; - Thermal drivers; - TTY drivers; - USB subsystem; - Framebuffer layer; - BTRFS file system; - Network file system server daemon; - NILFS2 file system; - File systems infrastructure; - Pstore file system; - SMB…