CVE-2026-43088net: af_key: zero aligned sockaddr tail in PF_KEY exports
- 5.5MediumCVSS base score
- 0.12%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: net: af_key: zero aligned sockaddr tail in PF_KEY exports PF_KEY export paths use `pfkey_sockaddr_size()` when reserving sockaddr payload space, so IPv6 addresses occupy 32 bytes on the wire. However, `pfkey_sockaddr_fill()` initializes only the first 28 bytes of `struct sockaddr_in6`, leaving the final 4 aligned bytes uninitialized. Not every PF_KEY message is affected. The state and policy dump builders already zero the whole message buffer before filling the sockaddr payloads. Keep the fix to the export paths that still append aligned sockaddr payloads with plain `skb_put()`: - `SADB_ACQUIRE` - `SADB_X_NAT_T_NEW_MAPPING` - `SADB_X_MIGRATE` Fix those paths by clearing only the aligned sockaddr tail after `pfkey_sockaddr_fill()`.
Timeline
ID reserved
By Linux
- 5 days later
· 5 days later
Published
- 6 months later
· 6 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.12% · top 98% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 6df5f90175fe4c584e9960b6c00131a7bf2b5399
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 746ee79d9e140f0e9e56f5123eaa88ad9332de7b
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e357c3cf8a44d4ec1f49ad6981e4ab9704354347
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 3c19cb8a84ef709d57943bd6664cf31cb91ba6ec
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 11cbf294bac623bd57296f231199193087f57b4a
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < edd446ee7cd3d02cac246168063d5b3e9ea68460
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2e74f974359b5382ecbe8536abbb5b837eb6c724
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 426c355742f02cf743b347d9d7dbdc1bfbfa31ef
- affected 2.6.12
- unaffected < 2.6.12
- unaffected 5.10.270 – ≤ 5.10.*
- unaffected 5.15.221 – ≤ 5.15.*
- unaffected 6.1.188 – ≤ 6.1.*
- unaffected 6.6.143 – ≤ 6.6.*
- unaffected 6.12.88 – ≤ 6.12.*
- unaffected 6.18.30 – ≤ 6.18.*
- unaffected 6.19.14 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References8
- https://git.kernel.org/stable/c/6df5f90175fe4c584e9960b6c00131a7bf2b5399 (opens in a new tab)
- https://git.kernel.org/stable/c/746ee79d9e140f0e9e56f5123eaa88ad9332de7b (opens in a new tab)
- https://git.kernel.org/stable/c/e357c3cf8a44d4ec1f49ad6981e4ab9704354347 (opens in a new tab)
- https://git.kernel.org/stable/c/3c19cb8a84ef709d57943bd6664cf31cb91ba6ec (opens in a new tab)
- https://git.kernel.org/stable/c/11cbf294bac623bd57296f231199193087f57b4a (opens in a new tab)
- https://git.kernel.org/stable/c/edd446ee7cd3d02cac246168063d5b3e9ea68460 (opens in a new tab)
- https://git.kernel.org/stable/c/2e74f974359b5382ecbe8536abbb5b837eb6c724 (opens in a new tab)
- https://git.kernel.org/stable/c/426c355742f02cf743b347d9d7dbdc1bfbfa31ef (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-27586 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-43088)Record last updated .