xfrm: ah: account for ESN high bits in async callbacks
Summary
| CVE | CVE-2026-46193 |
|---|
| State | PUBLISHED |
|---|
| Assigner | Linux |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2026-05-28 10:16:34 UTC |
|---|
| Updated | 2026-05-28 13:44:01 UTC |
|---|
| Description | In the Linux kernel, the following vulnerability has been resolved:
xfrm: ah: account for ESN high bits in async callbacks
AH allocates its temporary auth/ICV layout differently when ESN is enabled:
the async ahash setup appends a 4-byte seqhi slot before the ICV or
auth_data area, but the async completion callbacks still reconstruct the
temporary layout as if seqhi were absent.
With an async AH implementation selected, that makes AH copy or compare
the wrong bytes on both the IPv4 and IPv6 paths. In UML repro on IPv4 AH
with ESN and forced async hmac(sha1), ping fails with 100% packet loss,
and the callback logs show the pre-fix drift:
ah4 output_done: esn=1 err=0 icv_off=20 expected_off=24
ah4 input_done: esn=1 auth_off=20 expected_auth_off=24 icv_off=32 expected_icv_off=36
Reconstruct the callback-side layout the same way the setup path built it
by skipping the ESN seqhi slot before locating the saved auth_data or ICV.
Per RFC 4302, the ESN high-order 32 bits participate in the AH ICV
computation, so the async callbacks must account for the seqhi slot.
Post-fix, the same IPv4 AH+ESN+forced-async-hmac(sha1) UML repro shows
the corrected offset (ah4 output_done: esn=1 err=0 icv_off=24
expected_off=24) and ping succeeds; net/ipv4/ah4.o and net/ipv6/ah6.o
build clean at W=1. IPv6 AH+ESN was not exercised at runtime, and the
change has not been tested against a real async hardware AH engine. |
|---|
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected d4d573d0334d07341beffdcf97e2b85d3955d8ae 0555d4f526232b3c9e3afbcd490c0c0793aefec6 git |
Not specified |
| CNA |
Linux |
Linux |
affected d4d573d0334d07341beffdcf97e2b85d3955d8ae 729899a2aa8bda7844be0cdcd3b470f11b912eda git |
Not specified |
| CNA |
Linux |
Linux |
affected d4d573d0334d07341beffdcf97e2b85d3955d8ae 7db99a09b3bc87268287bc7ab5f2e7f382b5ad87 git |
Not specified |
| CNA |
Linux |
Linux |
affected d4d573d0334d07341beffdcf97e2b85d3955d8ae 2ffaa7a94f9a4d22724364a1821735a0231d9f8d git |
Not specified |
| CNA |
Linux |
Linux |
affected d4d573d0334d07341beffdcf97e2b85d3955d8ae ec54093e6a8f87e800bb6aa15eb7fc1e33faa524 git |
Not specified |
| CNA |
Linux |
Linux |
affected 3.15 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 3.15 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.140 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.88 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.30 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0.7 7.0.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1-rc3 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/729899a2aa8bda7844be0cdcd3b470f11b912eda |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/ec54093e6a8f87e800bb6aa15eb7fc1e33faa524 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/2ffaa7a94f9a4d22724364a1821735a0231d9f8d |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/0555d4f526232b3c9e3afbcd490c0c0793aefec6 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/7db99a09b3bc87268287bc7ab5f2e7f382b5ad87 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.
