net: guard timestamp cmsgs to real error queue skbs
- 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
- Fix
- Fixed in 4.11, 5.10.259, 5.15.210, 6.1.176, 6.6.143, and 3 more
- 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: net: guard timestamp cmsgs to real error queue skbs skb_is_err_queue() treats PACKET_OUTGOING as the sole marker for an skb from sk_error_queue. That assumption is not true for AF_PACKET sockets: outgoing packet taps are also delivered to packet sockets with skb->pkt_type == PACKET_OUTGOING, but their skb->cb is owned by AF_PACKET instead of struct sock_exterr_skb. If such an skb is received with timestamping enabled, the generic timestamp cmsg path can read AF_PACKET control-buffer state as sock_exterr_skb::opt_stats. With SO_RXQ_OVFL enabled, the packet drop counter overlaps opt_stats. An odd drop count makes the path emit SCM_TIMESTAMPING_OPT_STATS with skb->len and skb->data. For non-linear skbs this copies past the linear head and can trigger hardened usercopy or disclose adjacent heap contents. Keep skb_is_err_queue() local to net/socket.c, but make it verify that the PACKET_OUTGOING marker is paired with the sock_rmem_free destructor installed by sock_queue_err_skb(). AF_PACKET receive skbs use normal receive ownership and no longer pass as error-queue skbs, while legitimate sk_error_queue entries keep the PACKET_OUTGOING marker and sock_rmem_free ownership.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 8605330aac5a5785630aec8f64378a54891937cc · fixed in 24a0d548d3a765cd4558224e4f8e06e14cba26e3; From 8605330aac5a5785630aec8f64378a54891937cc · fixed in 71ff5cdd5da61d0438e902aa0fd68c28bc901abe; From 8605330aac5a5785630aec8f64378a54891937cc · fixed in ad9a0374ee6d11048e1f74cd5180bad58b9848b4; From 8605330aac5a5785630aec8f64378a54891937cc · fixed in b903e9b5629ec8dd6db92174070045bf81ad7060; From 8605330aac5a5785630aec8f64378a54891937cc · fixed in e0665b2a8e90bb08bd205062c75662b502d31797; From 8605330aac5a5785630aec8f64378a54891937cc · fixed in 3dde4fb941fa5649ab809f6cd3e20e0c424a4e31; From 8605330aac5a5785630aec8f64378a54891937cc · fixed in eb51a9ad3ceb01bc6c0fb608dbc856e03ee6f24a; From 8605330aac5a5785630aec8f64378a54891937cc · fixed in 1ee90b77b727df903033db873c75caac5c27ec98; From 4.10.14 · fixed in 4.11
- Linux Linux
4.11
- KernelLinux
From 4.11.0 · fixed in 5.10.259; From 5.11.0 · fixed in 5.15.210; From 5.16.0 · fixed in 6.1.176; From 6.2.0 · fixed in 6.6.143; From 6.7.0 · fixed in 6.12.94; From 6.13.0 · fixed in 6.18.36; From 6.19.0 · fixed in 7.0.13
References 8
git.kernel.org
- stable/c/24a0d548d3a765cd4558224e4f8e06e14cba26e3
- stable/c/71ff5cdd5da61d0438e902aa0fd68c28bc901abe
- stable/c/ad9a0374ee6d11048e1f74cd5180bad58b9848b4
- stable/c/b903e9b5629ec8dd6db92174070045bf81ad7060
- stable/c/e0665b2a8e90bb08bd205062c75662b502d31797
- stable/c/3dde4fb941fa5649ab809f6cd3e20e0c424a4e31
- stable/c/eb51a9ad3ceb01bc6c0fb608dbc856e03ee6f24a
- stable/c/1ee90b77b727df903033db873c75caac5c27ec98