CVE-2026-53260: tcp: Add preempt_{disable,enable}_nested() in reqsk_queue_hash_req().
Published Jun 25, 2026
·Updated
In the Linux kernel, the following vulnerability has been resolved:
Affected Software
10 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=6.12<7.0.13
Linux Linux kernel=7.1-rc1
Linux Linux kernel=7.1-rc2
Linux Linux kernel=7.1-rc3
Linux Linux kernel=7.1-rc4
Linux Linux kernel=7.1-rc5
Linux Linux kernel=7.1-rc6
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1
debian/linux-6.12
6.12.113-1~deb12u1
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.11-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.113-1~deb12u1
Event History
Jun 25, 2026
CVE Published
via MITRE·08:39 AM
Data Sourced
via MITRE·08:39 AM
DescriptionSeverity
Data Sourced
via NVD·09:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-53260?
The severity of CVE-2026-53260 is rated at risk level 37.
2
How do I fix CVE-2026-53260?
To fix CVE-2026-53260, update the Linux kernel to the latest patched version that addresses this vulnerability.
3
What systems are affected by CVE-2026-53260?
CVE-2026-53260 affects the Linux kernel, specifically the components related to TCP connection handling.
4
What type of vulnerability is CVE-2026-53260?
CVE-2026-53260 is classified as a Use After Free vulnerability.
5
When was CVE-2026-53260 published?
CVE-2026-53260 was published on June 25, 2026.