net: af_key: zero aligned sockaddr tail in PF_KEY exports
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
2.6.12
References 8
git.kernel.org
- stable/c/6df5f90175fe4c584e9960b6c00131a7bf2b5399
- stable/c/746ee79d9e140f0e9e56f5123eaa88ad9332de7b
- stable/c/e357c3cf8a44d4ec1f49ad6981e4ab9704354347
- stable/c/3c19cb8a84ef709d57943bd6664cf31cb91ba6ec
- stable/c/11cbf294bac623bd57296f231199193087f57b4a
- stable/c/edd446ee7cd3d02cac246168063d5b3e9ea68460
- stable/c/2e74f974359b5382ecbe8536abbb5b837eb6c724
- stable/c/426c355742f02cf743b347d9d7dbdc1bfbfa31ef