What happened
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()`.
Affected versions
Linux: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through before 6df5f90175fe4c584e9960b6c00131a7bf2b5399 (git); 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through before 746ee79d9e140f0e9e56f5123eaa88ad9332de7b (git); 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through before e357c3cf8a44d4ec1f49ad6981e4ab9704354347 (git); 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through before 3c19cb8a84ef709d57943bd6664cf31cb91ba6ec (git); 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through before 11cbf294bac623bd57296f231199193087f57b4a (git); 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through before edd446ee7cd3d02cac246168063d5b3e9ea68460 (git); 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through before 2e74f974359b5382ecbe8536abbb5b837eb6c724 (git); 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through before 426c355742f02cf743b347d9d7dbdc1bfbfa31ef (git); 2.6.12 Fixed: See vendor advisory.
Why it matters
Review the vendor advisory and exposure of the affected product to determine operational impact.
Detection & mitigation
- Apply vendor-provided updates or mitigations.
- Review affected product exposure and access logs.
Public PoC references
No public PoC reference has passed the current publication threshold.