PatchSiren cyber security CVE debrief
CVE-2026-74578 Linux CVE debrief
A vulnerability in the Linux kernel's crypto: algif_skcipher has been resolved. The AIO/async path in skcipher_recvmsg() passes the socket-wide ctx->iv directly into the skcipher request. After io_submit() the socket lock is dropped and the request is processed asynchronously, so a concurrent sendmsg(ALG_SET_IV) can overwrite ctx->iv and make the in-flight request run under an attacker-controlled IV.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- HIGH 7.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-16
- Original CVE updated
- 2026-10-16
- Advisory published
- 2026-08-16
- Advisory updated
- 2026-10-16
Who should care
Linux kernel developers and maintainers, Linux distribution maintainers, and users of Linux-based systems should be aware of this vulnerability. They should assess exposure, prioritize remediation for systems using the affected kernel versions, and verify affected kernel versions. Additionally, security teams and vulnerability management teams should review the vulnerability and implement necessary mitigations.
Why it matters
The vulnerability in the Linux kernel's crypto: algif_skcipher allows an unprivileged user to recover the plaintext of a concurrent operation. Defenders should assess exposure and prioritize remediation for systems using the affected kernel versions.
- An unprivileged user may be able to recover the plaintext of a concurrent operation.
- The vulnerability requires verification of affected versions and remediation priority.
- Defenders should assess exposure and prioritize remediation for systems using the affected kernel versions.
Technical summary
The vulnerability is caused by the use of a shared IV in the async path of skcipher_recvmsg(). This allows an attacker to overwrite the IV and make the in-flight request run under an attacker-controlled IV, potentially allowing an unprivileged user to recover the plaintext of a concurrent operation. The issue affects the Linux kernel's crypto: algif_skcipher component. Defenders should assess exposure and prioritize remediation for systems using the affected kernel versions. The vulnerability requires verification of affected versions and remediation priority.
Defensive priority
High
Recommended defensive actions
- Review and apply the patches provided by the Linux kernel maintainers.
- Restrict access to the affected system to prevent exploitation.
- Monitor system logs for suspicious activity.
- Perform a thorough review of the system's configuration and assess exposure.
- Implement compensating controls for exposed systems while remediation is scheduled and verified.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
- Review relevant monitoring, detection, and logs for exposed assets that need extra review.
Evidence notes
The vulnerability allows an unprivileged user to recover the plaintext of a concurrent operation. The issue is caused by the use of a shared IV in the async path of skcipher_recvmsg(). Evidence from the Linux kernel maintainers indicates that this vulnerability can be exploited in certain configurations. Defenders should verify affected kernel versions and assess exposure.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-74578 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-74578
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-74578 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-74578
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
crypto: algif_skcipher - force synchronous processing on trees without ctx->state
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/74xxx/CVE-2026-74578.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/bf09b0be8e851f050e98da702d247c14d81b591a
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/73dd3bf704ca6c20639de70c08e9a10bee904a95
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/f1a87ca0843d74482402a206ea2dfb315ee9acbd
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/7b91e51d0eb7cbb07f7f086f9176bd93dbbc85dd
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/60eafc7b08c6689ea3ad39eff8d97aefc8a087c7
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/d7860b682da55433b5da0591b0e4c1982ecd2689
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/b05defc41b27c7d0c05c45f67bf5b91c28f93669
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.