CVE-2026-53223

net: guard timestamp cmsgs to real error queue skbs

HIGH
7.1
CVSS Score
Published: June 25, 2026 at 08:39 AM UTC
Updated: October 19, 2026 at 08:19 PM UTC
4 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 CPU 1518-4 Pn /dp MFP FirmwareSiplus S7-1500 CPU 1518-4 Pn /dp MFP Firmware

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.10.14 ≤ v < 4.114.11.1 ≤ v < 5.10.2595.11 ≤ v < 5.15.2105.16 ≤ v < 6.1.1766.13 ≤ v < 6.18.366.19 ≤ v < 7.0.136.2 ≤ v < 6.6.1436.7 ≤ v < 6.12.944.10.144.114.11 rc44.11 rc54.11 rc64.11 rc74.11 rc87.17.1 rc17.1 rc27.1 rc37.1 rc47.1 rc57.1 rc67.1 rc78605330aac5a5785630aec8f64378a54891937cccdaf15b43bd31003220cb080bcbbd57787a2fca9
Vendor states this is fixed in 1ee90b77b727df903033db873c75caac5c27ec98 (fixed)
Vendor states this is fixed in 24a0d548d3a765cd4558224e4f8e06e14cba26e3 (fixed)
Vendor states this is fixed in 3dde4fb941fa5649ab809f6cd3e20e0c424a4e31 (fixed)
Vendor states this is fixed in 71ff5cdd5da61d0438e902aa0fd68c28bc901abe (fixed)
Vendor states this is fixed in ad9a0374ee6d11048e1f74cd5180bad58b9848b4 (fixed)
Vendor states this is fixed in b903e9b5629ec8dd6db92174070045bf81ad7060 (fixed)
Vendor states this is fixed in e0665b2a8e90bb08bd205062c75662b502d31797 (fixed)
Vendor states this is fixed in eb51a9ad3ceb01bc6c0fb608dbc856e03ee6f24a (fixed)
Vendor states this is fixed in 4.11 (unaffected)
Vendor states this is fixed in 5.10.259 (unaffected)
Vendor states this is fixed in 5.15.210 (unaffected)
Vendor states this is fixed in 6.1.176 (unaffected)
Vendor states this is fixed in 6.12.94 (unaffected)
Vendor states this is fixed in 6.18.36 (unaffected)
Vendor states this is fixed in 6.6.143 (unaffected)
Vendor states this is fixed in 7.0.13 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.1HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfoCWE-125

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card