CVE-2026-74577

net: mpls: initialize rtm_tos in mpls_getroute()

N/A
Published: August 15, 2026 at 12:28 PM UTC
Updated: August 19, 2026 at 05:21 PM UTC
1 product affected across 1 vendorLinux Kernel

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
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: net: mpls: initialize rtm_tos in mpls_getroute() mpls_getroute() builds the RTM_NEWROUTE reply to an RTM_GETROUTE request by filling a struct rtmsg allocated from an skb whose data area is not zeroed (alloc_skb(NLMSG_GOODSIZE, ...)). It sets every field of the header except rtm_tos: r = nlmsg_data(nlh); r->rtm_family = AF_MPLS; r->rtm_dst_len = 20; r->rtm_src_len = 0; r->rtm_table = RT_TABLE_MAIN; r->rtm_type = RTN_UNICAST; r->rtm_scope = RT_SCOPE_UNIVERSE; r->rtm_protocol = rt->rt_protocol; r->rtm_flags = 0; struct rtmsg has no padding, so the one uninitialised byte rtm_tos (offset 3) is copied straight to user space on recvmsg(), leaking a byte of uninitialised heap memory. This is in contrast to mpls_dump_route(), which fills the very same header and does set rtm_tos = 0. Initialize rtm_tos to 0, matching mpls_dump_route(). Reproduced with KMSAN by adding an MPLS route and issuing a non-RTM_F_FIB_MATCH RTM_GETROUTE for its label: BUG: KMSAN: kernel-infoleak in _copy_to_iter+0x36c/0x33f0 _copy_to_iter+0x36c/0x33f0 __skb_datagram_iter+0x196/0x12c0 skb_copy_datagram_iter+0x5b/0x210 netlink_recvmsg+0x37b/0xef0 ... Uninit was created at: __alloc_skb+0x8ca/0x10e0 mpls_getroute+0x1280/0x3a40 rtnetlink_rcv_msg+0x1138/0x15a0 ... Byte 19 of 64 is uninitialized (byte 19 = nlmsghdr(16) + rtmsg offset 3 = rtm_tos)

Affected

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

4.13 ≤ v < 5.10.2654.13 ≤ v < 5.15.2164.13 ≤ v < 6.1.1834.13 ≤ v < 6.12.1034.13 ≤ v < 6.18.444.13 ≤ v < 6.6.1514.13 ≤ v < 7.1.84.13 ≤ v < 7.2397fc9e5cefee0c33b86811fbddb0decb7288c524.13
Vendor states this is fixed in 1fea5ff0eb4aa7e951bb3d380248566c473aa377 (fixed)
Vendor states this is fixed in 248718fd88b146d8bdc7610ecd1eb4cd16e0b5a1 (fixed)
Vendor states this is fixed in 295dd295e2137e10e9a5b1891d97e0f08de76f03 (fixed)
Vendor states this is fixed in 2dc2fffc704a4365cae1aae078ba62223aaeff93 (fixed)
Vendor states this is fixed in 466b474a8deb0c93b5280c6d261e5eda6482eca7 (fixed)
Vendor states this is fixed in 95651461cf77cc6590fa08c87667717e5dcfa55d (fixed)
Vendor states this is fixed in a5cdd2407dd890f741f59b8367e4c6c101cce154 (fixed)
Vendor states this is fixed in ba56f88aab18d982f2a21f11390f4d8a8897782a (fixed)
Vendor states this is fixed in 4.13 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

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