Vulnerability · Published Feb 23, 2024 · Assigned by Linux
CVE-2024-26597net: qualcomm: rmnet: fix global oob in rmnet_policy
High 7.8
In plain English
A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 17% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: net: qualcomm: rmnet: fix global oob in rmnet_policy The variable rmnet_link_ops assign a *bigger* maxtype which leads to a global out-of-bounds read when parsing the netlink attributes. See bug trace below: ================================================================== BUG: KASAN: global-out-of-bounds in validate_nla lib/nlattr.c:386 [inline] BUG: KASAN: global-out-of-bounds in __nla_validate_parse+0x24af/0x2750 lib/nlattr.c:600 Read of size 1 at addr ffffffff92c438d0 by task syz-executor.6/84207 CPU: 0 PID: 84207 Comm: syz-executor.6 Tainted: G N 6.1.0 #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x8b/0xb3 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:284 [inline] print_report+0x172/0x475 mm/kasan/report.c:395 kasan_report+0xbb/0x1c0 mm/kasan/report.c:495 validate_nla lib/nlattr.c:386 [inline] __nla_validate_parse+0x24af/0x2750 lib/nlattr.c:600 __nla_parse+0x3e/0x50 lib/nlattr.c:697 nla_parse_nested_deprecated include/net/netlink.h:1248 [inline] __rtnl_newlink+0x50a/0x1880 net/core/rtnetlink.c:3485 rtnl_newlink+0x64/0xa0 net/core/rtnetlink.c:3594 rtnetlink_rcv_msg+0x43c/0xd70 net/core/rtnetlink.c:6091 netlink_rcv_skb+0x14f/0x410 net/netlink/af_netlink.c:2540 netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline] netlink_unicast+0x54e/0x800 net/netlink/af_netlink.c:1345 netlink_sendmsg+0x930/0xe50 net/netlink/af_netlink.c:1921 sock_sendmsg_nosec net/socket.c:714 [inline] sock_sendmsg+0x154/0x190 net/socket.c:734 ____sys_sendmsg+0x6df/0x840 net/socket.c:2482 ___sys_sendmsg+0x110/0x1b0 net/socket.c:2536 __sys_sendmsg+0xf3/0x1c0 net/socket.c:2565 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0x90 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fdcf2072359 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fdcf13e3168 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007fdcf219ff80 RCX: 00007fdcf2072359 RDX: 0000000000000000 RSI: 0000000020000200 RDI: 0000000000000003 RBP: 00007fdcf20bd493 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fffbb8d7bdf R14: 00007fdcf13e3300 R15: 0000000000022000 </TASK> The buggy address belongs to the variable: rmnet_policy+0x30/0xe0 The buggy address belongs to the physical page: page:0000000065bdeb3c refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x155243 flags: 0x200000000001000(reserved|node=0|zone=2) raw: 0200000000001000 ffffea00055490c8 ffffea00055490c8 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffffffff92c43780: f9 f9 f9 f9 00 00 00 02 f9 f9 f9 f9 00 00 00 07 ffffffff92c43800: f9 f9 f9 f9 00 00 00 05 f9 f9 f9 f9 06 f9 f9 f9 >ffffffff92c43880: f9 f9 f9 f9 00 00 00 00 00 00 f9 f9 f9 f9 f9 f9 ^ ffffffff92c43900: 00 00 00 00 00 00 00 00 07 f9 f9 f9 f9 f9 f9 f9 ffffffff92c43980: 00 00 00 07 f9 f9 f9 f9 00 00 00 05 f9 f9 f9 f9 According to the comment of `nla_parse_nested_deprecated`, the maxtype should be len(destination array) - 1. Hence use `IFLA_RMNET_MAX` here.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.76-1 | DEBIAN-CVE-2024-26597 |
| Debian:13 | linux | 6.6.15-1 | DEBIAN-CVE-2024-26597 |
| Debian:14 | linux | 6.6.15-1 | DEBIAN-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux | 5.15.0-102.112 | USN-6725-1 |
| Ubuntu:22.04:LTS | linux | 5.15.0-102.112 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1057.63 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1057.63 | USN-6725-2 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | 6.5.0-1016.16~22.04.1 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | 6.5.0-1016.16~22.04.1 | USN-6707-3 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1060.69 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1060.69 | USN-6725-1 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | 6.5.0-1017.17~22.04.1 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | 6.5.0-1017.17~22.04.1 | USN-6707-4 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1060.69.1 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1060.69.1 | USN-6725-1 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1055.63 | USN-6725-1 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1055.63 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | 6.5.0-1016.16~22.04.1 | USN-6707-1 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | 6.5.0-1016.16~22.04.1 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1054.59 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1054.59 | USN-6725-1 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1040.46 | USN-6725-1 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1040.46 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | 6.5.0-26.26~22.04.1 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | 6.5.0-26.26~22.04.1 | USN-6707-1 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1050.53 | USN-6725-1 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1050.53 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1052.58 | USN-6725-1 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1052.58 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1054.59 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1054.59 | USN-6725-1 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-102.112 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-102.112 | USN-6725-1 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | 6.5.0-26.26.1~22.04.1 | USN-6707-1 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | 6.5.0-26.26.1~22.04.1 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1048.48 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1048.48 | USN-6725-1 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | 6.5.0-1014.14 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1025.25 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1012.12 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | 6.1.0-1035.35 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | 6.5.0-1018.19 | USN-6707-1 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | 6.5.0-1018.19 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1055.61 | USN-6725-1 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1055.61 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | 6.5.0-1019.19~22.04.1 | USN-6707-1 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | 6.5.0-1019.19~22.04.1 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1050.53 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1050.53 | USN-6725-1 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | 6.5.0-26.26.1~22.04.1 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | 6.5.0-1010.11~22.04.1 | USN-6707-1 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | 6.5.0-1010.11~22.04.1 | UBUNTU-CVE-2024-26597 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1030.34 | UBUNTU-CVE-2024-26597 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 14452ca3b5ce304fb2fea96dbc9ca1e4e7978551 – before 093dab655808207f7a9f54cf156240aeafc7059014452ca3b5ce304fb2fea96dbc9ca1e4e7978551 – before 02467ab8b404d80429107588e0f3425cf5fcd2e514452ca3b5ce304fb2fea96dbc9ca1e4e7978551 – before 2295c22348faf795e1ccdf618f6eb7afdb2f744714452ca3b5ce304fb2fea96dbc9ca1e4e7978551 – before 3b5254862258b595662a0ccca6e9eeb88d6e746814452ca3b5ce304fb2fea96dbc9ca1e4e7978551 – before ee1dc3bf86f2df777038506b139371a9add0253414452ca3b5ce304fb2fea96dbc9ca1e4e7978551 – before c4734535034672f59f2652e1e0058c490da62a5c14452ca3b5ce304fb2fea96dbc9ca1e4e7978551 – before 17d06a5c44d8fd2e8e61bac295b09153496f87e114452ca3b5ce304fb2fea96dbc9ca1e4e7978551 – before b33fb5b801c6db408b774a68e7c8722796b59ecc |
| Linux | Linux | 4.17 |
References
- https://git.kernel.org/stable/c/093dab655808207f7a9f54cf156240aeafc70590
- https://git.kernel.org/stable/c/02467ab8b404d80429107588e0f3425cf5fcd2e5
- https://git.kernel.org/stable/c/2295c22348faf795e1ccdf618f6eb7afdb2f7447
- https://git.kernel.org/stable/c/3b5254862258b595662a0ccca6e9eeb88d6e7468
- https://git.kernel.org/stable/c/ee1dc3bf86f2df777038506b139371a9add02534
- https://git.kernel.org/stable/c/c4734535034672f59f2652e1e0058c490da62a5c
- https://git.kernel.org/stable/c/17d06a5c44d8fd2e8e61bac295b09153496f87e1
- https://git.kernel.org/stable/c/b33fb5b801c6db408b774a68e7c8722796b59ecc
- https://lists.debian.org/debian-lts-announce/2024/06/msg00016.html x_transferred
- https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html x_transferred