ipmr: do not call mr_mfc_uses_dev() for unres entries
- 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.4.291, 5.10.235, 5.15.179, 6.1.129, 6.6.76, 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: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: ipmr: do not call mr_mfc_uses_dev() for unres entries syzbot found that calling mr_mfc_uses_dev() for unres entries would crash [1], because c->mfc_un.res.minvif / c->mfc_un.res.maxvif alias to "struct sk_buff_head unresolved", which contain two pointers. This code never worked, lets remove it. [1] Unable to handle kernel paging request at virtual address ffff5fff2d536613 KASAN: maybe wild-memory-access in range [0xfffefff96a9b3098-0xfffefff96a9b309f] Modules linked in: CPU: 1 UID: 0 PID: 7321 Comm: syz.0.16 Not tainted 6.13.0-rc7-syzkaller-g1950a0af2d55 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : mr_mfc_uses_dev net/ipv4/ipmr_base.c:290 [inline] pc : mr_table_dump+0x5a4/0x8b0 net/ipv4/ipmr_base.c:334 lr : mr_mfc_uses_dev net/ipv4/ipmr_base.c:289 [inline] lr : mr_table_dump+0x694/0x8b0 net/ipv4/ipmr_base.c:334 Call trace: mr_mfc_uses_dev net/ipv4/ipmr_base.c:290 [inline] (P) mr_table_dump+0x5a4/0x8b0 net/ipv4/ipmr_base.c:334 (P) mr_rtm_dumproute+0x254/0x454 net/ipv4/ipmr_base.c:382 ipmr_rtm_dumproute+0x248/0x4b4 net/ipv4/ipmr.c:2648 rtnl_dump_all+0x2e4/0x4e8 net/core/rtnetlink.c:4327 rtnl_dumpit+0x98/0x1d0 net/core/rtnetlink.c:6791 netlink_dump+0x4f0/0xbc0 net/netlink/af_netlink.c:2317 netlink_recvmsg+0x56c/0xe64 net/netlink/af_netlink.c:1973 sock_recvmsg_nosec net/socket.c:1033 [inline] sock_recvmsg net/socket.c:1055 [inline] sock_read_iter+0x2d8/0x40c net/socket.c:1125 new_sync_read fs/read_write.c:484 [inline] vfs_read+0x740/0x970 fs/read_write.c:565 ksys_read+0x15c/0x26c fs/read_write.c:708
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From cb167893f41e21e6bd283d78e53489289dc0592d · fixed in 71a0fcb68c0a5f3ec912b540cd5d72148e6ee5f1; From cb167893f41e21e6bd283d78e53489289dc0592d · fixed in 53df27fd38f84bd3cd6b004eb4ff3c4903114f1d; From cb167893f41e21e6bd283d78e53489289dc0592d · fixed in 547ef7e8cbb98f966c8719a3e15d4e078aaa9b47; From cb167893f41e21e6bd283d78e53489289dc0592d · fixed in 57177c5f47a8da852f8d76cf6945cf803f8bb9e5; From cb167893f41e21e6bd283d78e53489289dc0592d · fixed in b379b3162ff55a70464c6a934ae9bf0497478a62; From cb167893f41e21e6bd283d78e53489289dc0592d · fixed in a099834a51ccf9bbba3de86a251b3433539abfde; From cb167893f41e21e6bd283d78e53489289dc0592d · fixed in 26bb7d991f04eeef47dfad23e533834995c26f7a; From cb167893f41e21e6bd283d78e53489289dc0592d · fixed in 15a901361ec3fb1c393f91880e1cbf24ec0a88bd
- Linux Linux
4.20
- KernelLinux
From 4.20.0 · fixed in 5.4.291; From 5.5.0 · fixed in 5.10.235; From 5.11.0 · fixed in 5.15.179; From 5.16.0 · fixed in 6.1.129; From 6.2.0 · fixed in 6.6.76; From 6.7.0 · fixed in 6.12.13; From 6.13.0 · fixed in 6.13.2
References 8
git.kernel.org
- stable/c/71a0fcb68c0a5f3ec912b540cd5d72148e6ee5f1
- stable/c/53df27fd38f84bd3cd6b004eb4ff3c4903114f1d
- stable/c/547ef7e8cbb98f966c8719a3e15d4e078aaa9b47
- stable/c/57177c5f47a8da852f8d76cf6945cf803f8bb9e5
- stable/c/b379b3162ff55a70464c6a934ae9bf0497478a62
- stable/c/a099834a51ccf9bbba3de86a251b3433539abfde
- stable/c/26bb7d991f04eeef47dfad23e533834995c26f7a
- stable/c/15a901361ec3fb1c393f91880e1cbf24ec0a88bd