CVE-2026-64345·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_printer: take kref only for successful open printer_open() returns -EBUSY when the character device is already open, but it increments dev->kref regardless of the return value. VFS does not call ->release() for a failed open, so every rejected second open permanently leaks one reference. Move kref_get() into the successful-open branch.
- Severity
- medium
- Software
- Kernel
- Fixed in
- 7.1.4
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.12% — higher than 2% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Affected versions
From: 6.19
Until: 7.1.4
Fixed in: 7.1.4
How to fix this CVE
Update your Linux kernel to version 7.1.4 or later to resolve a reference counting leak in the USB printer gadget driver. This vulnerability causes memory leaks when multiple open attempts are made on the printer character device. Apply the patch through your distribution's standard kernel update mechanism as soon as possible.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Check installed kernel version: uname -r (should be 7.1.4 or later; vulnerable if between 6.19 and 7.1.3)
- Verify USB printer gadget module is loaded: lsmod | grep g_printer (if output appears, the vulnerable component may be active)
- Monitor kernel logs for repeated EBUSY errors on printer device: dmesg | grep -i 'printer.*busy' or journalctl -k | grep printer
- Confirm patch applied after update: uname -r should show version 7.1.4 or higher; verify with grep -i 'kref_get' in /boot/config-$(uname -r) that proper refcount handling is in place
FAQ
What is CVE-2026-64345?
This vulnerability exists in the Linux kernel's USB printer gadget driver where the reference counter is incremented even when a device open operation fails due to the device already being in use, causing a permanent memory leak with each rejected concurrent access attempt.
Is CVE-2026-64345 being actively exploited?
No, this vulnerability is not listed in the CISA KEV catalog and has no public exploits available. However, it should still be patched to prevent resource exhaustion.
What versions of Kernel are affected by CVE-2026-64345?
Kernel versions 6.19 through 7.1.3 are vulnerable. Kernel 7.1.4 and later include the fix.
How do I check if my server is vulnerable to CVE-2026-64345?
Run 'uname -r' to check your kernel version. If the output shows a version between 6.19 and 7.1.3 inclusive, your system is vulnerable.
Does Defensia detect CVE-2026-64345?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2026-64345 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/30adce93d5c4a5a1ec29d9249e3fdfcc391d406b
- https://git.kernel.org/stable/c/75c0ad13e136961328253742501b4efc3988a587
- https://git.kernel.org/stable/c/7f1f24c367938c5537e2308bf9a965f051d14774
- https://git.kernel.org/stable/c/8a5eba992c862b0c94411eecf9b7121e8636db38
- https://git.kernel.org/stable/c/94ec20d97aa51547965a539f660a1fe79c6929a3
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-64345. Free for 1 server.
Get started free