tipc: fix u16 MTU truncation in media and bearer MTU validation
- 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 5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, and 2 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: total
Summary
In the Linux kernel, the following vulnerability has been resolved: tipc: fix u16 MTU truncation in media and bearer MTU validation Both TIPC_NL_MEDIA_SET and TIPC_NL_BEARER_SET accept user-supplied MTU values but only enforce a minimum bound, not a maximum. When a user sets the MTU to a value exceeding U16_MAX (65535), it passes validation but is silently truncated when assigned to u16 fields l->mtu and l->advertised_mtu in tipc_link_create(). Values like 65536 (0x10000) truncate to 0, causing a division by zero in tipc_link_set_queue_limits() which computes TIPC_MAX_PUBL / (l->mtu / ITEM_SIZE). Other overflowing values (e.g. 65537-131071) produce small incorrect MTU values, resulting in link malfunction behaviors. Crash stack (triggered as unprivileged user via user namespace): tipc_link_set_queue_limits net/tipc/link.c:2531 tipc_link_create net/tipc/link.c:520 tipc_node_check_dest net/tipc/node.c:1279 tipc_disc_rcv net/tipc/discover.c:252 tipc_rcv net/tipc/node.c:2129 tipc_udp_recv net/tipc/udp_media.c:392 Two independent paths lack the upper bound check: 1. tipc_udp_mtu_bad() -- called from __tipc_nl_media_set() (MEDIA_SET) 2. inline check in __tipc_nl_bearer_set() at bearer.c:1160 (BEARER_SET) Fix both by rejecting MTU values above U16_MAX.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 901271e0403af638c224987c2a4e55cebade7e91 · fixed in 8bfdfe0dbb36a650b7c4dec1aeae078319938a0b; From 901271e0403af638c224987c2a4e55cebade7e91 · fixed in dc4b577a083b361d25e118dc96d8281255ebe22c; From 901271e0403af638c224987c2a4e55cebade7e91 · fixed in dfdfd987f1917c84766e097a6120a1f3f1634940; From 901271e0403af638c224987c2a4e55cebade7e91 · fixed in f02334a9e378f7e07232b26dc3d2ab353339f040; From 901271e0403af638c224987c2a4e55cebade7e91 · fixed in f4013598b69457dbea350df52e52daea6faef8eb; From 901271e0403af638c224987c2a4e55cebade7e91 · fixed in 1b8fb5a20508bfb0db854e01214888c761b3a911; From 901271e0403af638c224987c2a4e55cebade7e91 · fixed in c1cda72f6acec02ebd45d913bf8527ff77336ba6; From 901271e0403af638c224987c2a4e55cebade7e91 · fixed in 9f29cd8a8e7901a2617c8064ce9f50fc67b97cb8
- Linux Linux
4.18
- KernelLinux
From 4.18.0 · fixed in 5.10.265; From 5.11.0 · fixed in 5.15.216; From 5.16.0 · fixed in 6.1.183; From 6.2.0 · fixed in 6.6.148; From 6.7.0 · fixed in 6.12.101; From 6.13.0 · fixed in 6.18.42; From 6.19.0 · fixed in 7.1.6
References 8
git.kernel.org
- stable/c/8bfdfe0dbb36a650b7c4dec1aeae078319938a0b
- stable/c/dc4b577a083b361d25e118dc96d8281255ebe22c
- stable/c/dfdfd987f1917c84766e097a6120a1f3f1634940
- stable/c/f02334a9e378f7e07232b26dc3d2ab353339f040
- stable/c/f4013598b69457dbea350df52e52daea6faef8eb
- stable/c/1b8fb5a20508bfb0db854e01214888c761b3a911
- stable/c/c1cda72f6acec02ebd45d913bf8527ff77336ba6
- stable/c/9f29cd8a8e7901a2617c8064ce9f50fc67b97cb8