Local service interruption via TCP sysctl race
Published Feb 26, 2025 · Updated May 11, 2026
Race condition in Linux kernel TCP reordering code allows local users to interrupt service by racing a network sysctl. The tcp_check_sack_reordering() and tcp_check_reno_reordering() readers access sysctl_tcp_max_reordering without READ_ONCE(), permitting a concurrent write to yield an inconsistent value. Exploitation requires local low-privilege access and a difficult race; service interruption is the published consequence, while the precise failure mode is undisclosed.
Summary
What happened
Race condition in Linux kernel TCP reordering code allows local users to interrupt service by racing a network sysctl. The tcp_check_sack_reordering() and tcp_check_reno_reordering() readers access sysctl_tcp_max_reordering without READ_ONCE(), permitting a concurrent write to yield an inconsistent value. Exploitation requires local low-privilege access and a difficult race; service interruption is the published consequence, while the precise failure mode is undisclosed.
The record
- CVE
- CVE-2022-49571
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362, CAPEC-26, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.19
- Affected versionversion=dca145ffaa8d39ea1904491ac81b92b7049372c0 <064852663308c801861bd54789d81421fa4c2928
- Affected versionversion=dca145ffaa8d39ea1904491ac81b92b7049372c0 <46deb91ac8a790286ad6d24cf92e7ab0ab2582bb
- Affected versionversion=dca145ffaa8d39ea1904491ac81b92b7049372c0 <50a1d3d097503a90cf84ebe120afcde37e9c33b3
- Affected versionversion=dca145ffaa8d39ea1904491ac81b92b7049372c0 <5e38cee24f19d19280c68f1ac8bf6790d607f60a
- Affected versionversion=dca145ffaa8d39ea1904491ac81b92b7049372c0 <a11e5b3e7a59fde1a90b0eaeaa82320495cf8cae
- Affected versionversion=dca145ffaa8d39ea1904491ac81b92b7049372c0 <ce3731c61589ed73364a5b55ce34131762ef9b60
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo