crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 5.10.245, 5.15.194, 6.1.154, 6.6.108, 6.12.49, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: active
- Automatable: no
- Technical impact: total
Summary
The Linux kernel's AF_ALG (crypto user-space interface) socket code is affected. Concurrent write operations to the same AF_ALG socket could interleave data unpredictably and corrupt the socket's internal state, which may lead to incorrect cryptographic results or instability.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
In the Linux kernel, the following vulnerability has been resolved: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg Issuing two writes to the same af_alg socket is bogus as the data will be interleaved in an unpredictable fashion. Furthermore, concurrent writes may create inconsistencies in the internal socket state. Disallow this by adding a new ctx->write field that indiciates exclusive ownership for writing.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: active · Automatable: no · Technical impact: total
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
Affected versions
- Linux Linux
From 8ff590903d5fc7f5a0a988c38267a3d08e6393a2 · fixed in 0f28c4adbc4a97437874c9b669fd7958a8c6d6ce; From 8ff590903d5fc7f5a0a988c38267a3d08e6393a2 · fixed in e4c1ec11132ec466f7362a95f36a506ce4dc08c9; From 8ff590903d5fc7f5a0a988c38267a3d08e6393a2 · fixed in 1f323a48e9b5ebfe6dc7d130fdf5c3c0e92a07c8; From 8ff590903d5fc7f5a0a988c38267a3d08e6393a2 · fixed in 7c4491b5644e3a3708f3dbd7591be0a570135b84; From 8ff590903d5fc7f5a0a988c38267a3d08e6393a2 · fixed in 9aee87da5572b3a14075f501752e209801160d3d; From 8ff590903d5fc7f5a0a988c38267a3d08e6393a2 · fixed in 45bcf60fe49b37daab1acee57b27211ad1574042; From 8ff590903d5fc7f5a0a988c38267a3d08e6393a2 · fixed in 1b34cbbf4f011a121ef7b2d7d6e6920a036d5285
- Linux Linux
2.6.38
- KernelLinux
From 2.6.38 · fixed in 5.10.245; From 5.11.0 · fixed in 5.15.194; From 5.16.0 · fixed in 6.1.154; From 6.2.0 · fixed in 6.6.108; From 6.7.0 · fixed in 6.12.49; From 6.13.0 · fixed in 6.16.9
References 7
git.kernel.org
- stable/c/0f28c4adbc4a97437874c9b669fd7958a8c6d6ce
- stable/c/e4c1ec11132ec466f7362a95f36a506ce4dc08c9
- stable/c/1f323a48e9b5ebfe6dc7d130fdf5c3c0e92a07c8
- stable/c/7c4491b5644e3a3708f3dbd7591be0a570135b84
- stable/c/9aee87da5572b3a14075f501752e209801160d3d
- stable/c/45bcf60fe49b37daab1acee57b27211ad1574042
- stable/c/1b34cbbf4f011a121ef7b2d7d6e6920a036d5285