CVE-2026-46028: crypto: algif_aead - snapshot IV for async AEAD requests
In the Linux kernel, the following vulnerability has been resolved:
crypto: algif_aead - snapshot IV for async AEAD requests
AF_ALG AEAD AIO requests currently use the socket-wide IV buffer during
request processing. For async requests, later socket activity can
update that shared state before the original request has fully
completed, which can lead to inconsistent IV handling.
Snapshot the IV into per-request storage when preparing the AEAD
request, so in-flight operations no longer depend on mutable socket
state.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel cryptographic handling flaw. Async AF_ALG AEAD operations could keep using a shared IV buffer after later socket activity changed it, causing inconsistent encryption or authentication behavior. The public record does not provide CVSS, confirmed impact, or active exploitation evidence.
Executive priority
Treat this as a kernel maintenance item until severity is clarified. Prioritize normal patch cycles, with faster handling on multi-user, container, or untrusted workload hosts. Current sources do not support emergency response language.
Technical view
AF_ALG AEAD AIO requests used socket-wide IV state during request processing. For async requests, another operation could mutate that socket IV before completion. The fix snapshots the IV into per-request storage so in-flight AEAD work no longer depends on mutable socket state.
Likely exposure
Exposure appears limited to Linux systems where local software uses AF_ALG AEAD asynchronous requests. The source bundle does not indicate remote network exposure by default, affected distributions, or whether containers materially change reachability.
Exploitation context
The CVE is not listed as KEV in the provided data, and no cited source states active exploitation. The bundle gives a bug class and kernel fixes, but not a proof of exploitation, attack preconditions, or real-world abuse reports.
Researcher notes
Key uncertainty is impact. The public text describes inconsistent IV handling, which may affect cryptographic correctness, but does not define confidentiality, integrity, privilege, or denial-of-service outcomes. Validate against upstream commits and downstream advisories.
Mitigation direction
Apply the relevant Linux stable or distribution kernel update containing the referenced fix.
Track vendor advisories for exact affected package versions and supported remediation guidance.
Prioritize hosts running untrusted local workloads or software using kernel AF_ALG crypto.
If patching is delayed, check vendor guidance for supported temporary controls.
Validation and detection
Inventory running kernel versions across Linux assets.
Confirm vendor packages include the CVE-2026-46028 fix or referenced stable commits.
Review systems for applications or services using AF_ALG AEAD asynchronous operations.
Check vulnerability scanner findings against distribution-specific advisories before closure.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-46028 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
9Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 27, 2026, 12:56 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.