PT-2025-35999

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The Linux kernel contains a flaw in the ftgmac100 phy disconnect function within the ftgmac100 module. A potential NULL pointer access could occur because netdev-phydev is reset to NULL...

kernel: ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead

In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix NULL pointer dereference in isftracetrampoline when ftrace is dead ftracestartup does not remove ops from ftraceopslist when ftracestartupenable fails: registerftracefunction ftracestartup registerftracefunction...

UBUNTU-CVE-2025-38385

In the Linux kernel, the following vulnerability has been resolved: net: usb: lan78xx: fix WARN in netifnapidellocked on disconnect Remove redundant netifnapidel call from disconnect path. A WARN may be triggered in netifnapidellocked during USB device disconnect: WARNING: CPU: 0 PID: 11 at...

UBUNTU-CVE-2025-38394

In the Linux kernel, the following vulnerability has been resolved: HID: appletb-kbd: fix memory corruption of inputhandlerlist In appletbkbdprobe an input handler is initialised and then registered with input core through inputregisterhandler. When this happens input core will add the input...

CVE-2025-38394

In the Linux kernel, the following vulnerability has been resolved: HID: appletb-kbd: fix memory corruption of inputhandlerlist In appletbkbdprobe an input handler is initialised and then registered with input core through inputregisterhandler. When this happens input core will add the input...

CVE-2025-38394 HID: appletb-kbd: fix memory corruption of input_handler_list

In the Linux kernel, the following vulnerability has been resolved: HID: appletb-kbd: fix memory corruption of inputhandlerlist In appletbkbdprobe an input handler is initialised and then registered with input core through inputregisterhandler. When this happens input core will add the input...

PT-2025-35955

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A double-free vulnerability exists in the i2c core, specifically within the i2c unregister device function. This issue occurs when an i2c client has a software fwnode as its primary node...

SUSE CVE-2025-38305

In the Linux kernel, the following vulnerability has been resolved: ptp: remove ptp-nvclocks check logic in ptpvclockinuse There is no disagreement that we should check both ptp-isvirtualclock and ptp-nvclocks to check if the ptp virtual clock is in use. However, when we acquire ptp-nvclocksmux t...

net: dsa: mv88e6xxx: avoid unregistering devlink regions which were never registered

...

netfilter: nf_tables: don't unregister hook when table is dormant

...

SUSE CVE-2025-38250

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hcicore: Fix use-after-free in vhciflush syzbot reported use-after-free in vhciflush without repro. 0 From the splat, a thread closed a vhci file descriptor while its device was being used by iotcl on another thread...

DEBIAN-CVE-2025-38250

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hcicore: Fix use-after-free in vhciflush syzbot reported use-after-free in vhciflush without repro. 0 From the splat, a thread closed a vhci file descriptor while its device was being used by iotcl on another thread...

AZL-70495 CVE-2025-38250 affecting package kernel 5.15.200.1-1

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hcicore: Fix use-after-free in vhciflush syzbot reported use-after-free in vhciflush without repro. 0 From the splat, a thread closed a vhci file descriptor while its device was being used by iotcl on another thread...

AZL-64847 CVE-2025-38250 affecting package kernel for versions less than 6.6.104.2-1

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hcicore: Fix use-after-free in vhciflush syzbot reported use-after-free in vhciflush without repro. 0 From the splat, a thread closed a vhci file descriptor while its device was being used by iotcl on another thread...

UBUNTU-CVE-2025-38250

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hcicore: Fix use-after-free in vhciflush syzbot reported use-after-free in vhciflush without repro. 0 From the splat, a thread closed a vhci file descriptor while its device was being used by iotcl on another thread...

kernel: Bluetooth: hci_sync: Fix queuing commands when HCI_UNREGISTER is set

A vulnerability was found in the Linux kernel's Bluetooth subsystem in the hcicmdsyncqueue function. There was a missing check for whether the HCIUNREGISTER flag had been set, meaning that commands were still sent even as the Bluetooth device was being unregistered. This issue could lead to a...

kernel: Bluetooth: hci_sync: Fix queuing commands when HCI_UNREGISTER is set

A vulnerability was found in the Linux kernel's Bluetooth subsystem in the hcicmdsyncqueue function. There was a missing check for whether the HCIUNREGISTER flag had been set, meaning that commands were still sent even as the Bluetooth device was being unregistered. This issue could lead to a...

SUSE CVE-2025-38116

In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: fix uaf in ath12kcoreinit When the execution of ath12kcorehwgroupassign or ath12kcorehwgroupcreate fails, the registered notifier chain is not unregistered properly. Its memory is freed after rmmod, which may trigge...

DEBIAN-CVE-2025-38137

In the Linux kernel, the following vulnerability has been resolved: PCI/pwrctrl: Cancel outstanding rescan work when unregistering It's possible to trigger use-after-free here by: a forcing rescanworkfunc to take a long time and b utilizing a pwrctrl driver that may be unloaded for some reason...

UBUNTU-CVE-2025-38137

In the Linux kernel, the following vulnerability has been resolved: PCI/pwrctrl: Cancel outstanding rescan work when unregistering It's possible to trigger use-after-free here by: a forcing rescanworkfunc to take a long time and b utilizing a pwrctrl driver that may be unloaded for some reason...