CVE-2026-43384: net/tcp-ao: Fix MAC comparison to be constant-time
In the Linux kernel, the following vulnerability has been resolved:
net/tcp-ao: Fix MAC comparison to be constant-time
To prevent timing attacks, MACs need to be compared in constant
time. Use the appropriate helper function for this.
Security readout for executives and security teams
Plain-English summary
Linux TCP Authentication Option code compared authentication tags in a way that could leak information through response timing. An attacker able to collect sufficiently precise measurements might infer authentication information, weakening protected TCP sessions. The supplied record rates this critical, but it provides no evidence of successful exploitation or broad real-world impact.
Executive priority
Prioritize rapid exposure assessment because the supplied CVSS is 9.8, while calibrating urgency to actual TCP-AO use. Patch reachable TCP-AO deployments through supported vendor channels promptly. Broad emergency action across Linux estates is not justified by the bundle alone without confirming that the vulnerable feature is used.
Technical view
The Linux kernel TCP-AO implementation used a non-constant-time MAC comparison. Differences in comparison time can create a side channel when processing attacker-controlled authentication tags. The referenced stable-kernel changes replace that comparison with an appropriate constant-time helper. The bundle does not establish practical attack requirements, measurement reliability, or demonstrated key recovery.
Likely exposure
Exposure is most relevant to Linux systems using TCP-AO on attacker-reachable TCP connections. Systems not using TCP-AO are unlikely to exercise the vulnerable comparison path. The supplied version data is ambiguous and includes hashes and loosely structured releases, so confirm exposure using distribution-specific advisories and kernel package mappings.
Exploitation context
The record is not listed in KEV, and the supplied sources do not report active exploitation or a public proof of concept. Exploitation of a timing side channel would generally require repeated interactions and sufficiently reliable timing observations. Practical feasibility across real networks is not established by this bundle.
Researcher notes
The core defect is a timing-sensitive equality check in TCP-AO MAC verification. The bundle identifies four stable-kernel fixes but does not clearly map every affected or corrected release. Treat practical exploitability, required sample volume, network-noise tolerance, and security impact as unresolved research questions; do not interpret the CVSS vector as proof of demonstrated compromise.
Mitigation direction
Apply a vendor-supported kernel update containing the referenced constant-time comparison fix.
Check Linux distribution advisories for package-specific fixed versions and backports.
Restrict attacker reachability to TCP-AO-protected endpoints where operationally feasible.
Review whether TCP-AO is enabled and required on affected systems.
Validation and detection
Inventory running kernel versions on systems that configure or use TCP-AO.
Map installed kernel packages against distribution advisories and referenced stable commits.
Confirm updated kernels are running after patching, including following required reboots.
Verify the TCP-AO MAC comparison uses the constant-time helper in maintained source packages.
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-43384 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.
1CVSS vectors
3Timeline events
0ADP providers
5Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.