[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025011516-CVE-2024-57901-1f9e@gregkh>
Date: Wed, 15 Jan 2025 14:06:24 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-57901: af_packet: fix vlan_get_protocol_dgram() vs MSG_PEEK
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
af_packet: fix vlan_get_protocol_dgram() vs MSG_PEEK
Blamed commit forgot MSG_PEEK case, allowing a crash [1] as found
by syzbot.
Rework vlan_get_protocol_dgram() to not touch skb at all,
so that it can be used from many cpus on the same skb.
Add a const qualifier to skb argument.
[1]
skbuff: skb_under_panic: text:ffffffff8a8ccd05 len:29 put:14 head:ffff88807fc8e400 data:ffff88807fc8e3f4 tail:0x11 end:0x140 dev:<NULL>
------------[ cut here ]------------
kernel BUG at net/core/skbuff.c:206 !
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 1 UID: 0 PID: 5892 Comm: syz-executor883 Not tainted 6.13.0-rc4-syzkaller-00054-gd6ef8b40d075 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:skb_panic net/core/skbuff.c:206 [inline]
RIP: 0010:skb_under_panic+0x14b/0x150 net/core/skbuff.c:216
Code: 0b 8d 48 c7 c6 86 d5 25 8e 48 8b 54 24 08 8b 0c 24 44 8b 44 24 04 4d 89 e9 50 41 54 41 57 41 56 e8 5a 69 79 f7 48 83 c4 20 90 <0f> 0b 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3
RSP: 0018:ffffc900038d7638 EFLAGS: 00010282
RAX: 0000000000000087 RBX: dffffc0000000000 RCX: 609ffd18ea660600
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffff88802483c8d0 R08: ffffffff817f0a8c R09: 1ffff9200071ae60
R10: dffffc0000000000 R11: fffff5200071ae61 R12: 0000000000000140
R13: ffff88807fc8e400 R14: ffff88807fc8e3f4 R15: 0000000000000011
FS: 00007fbac5e006c0(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fbac5e00d58 CR3: 000000001238e000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
skb_push+0xe5/0x100 net/core/skbuff.c:2636
vlan_get_protocol_dgram+0x165/0x290 net/packet/af_packet.c:585
packet_recvmsg+0x948/0x1ef0 net/packet/af_packet.c:3552
sock_recvmsg_nosec net/socket.c:1033 [inline]
sock_recvmsg+0x22f/0x280 net/socket.c:1055
____sys_recvmsg+0x1c6/0x480 net/socket.c:2803
___sys_recvmsg net/socket.c:2845 [inline]
do_recvmmsg+0x426/0xab0 net/socket.c:2940
__sys_recvmmsg net/socket.c:3014 [inline]
__do_sys_recvmmsg net/socket.c:3037 [inline]
__se_sys_recvmmsg net/socket.c:3030 [inline]
__x64_sys_recvmmsg+0x199/0x250 net/socket.c:3030
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
The Linux kernel CVE team has assigned CVE-2024-57901 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.4.282 with commit c77064e76c768fb101ea5ff92dc771142fc9d8fd and fixed in 5.4.289 with commit 560cbdd26b510626f3f4f27d34c44dfd3dd3499d
Issue introduced in 5.10.224 with commit 83e2dfadcb6258fe3111c8a8ec9cf34465e55e64 and fixed in 5.10.233 with commit 0d3fa6c3c9ca7aa255696150f5b759ac4a4974e1
Issue introduced in 5.15.165 with commit d0a1f9aa70f0d8a05b6320e8a3f3b83adab8dac3 and fixed in 5.15.176 with commit de4f8d477c67ec1d7c28f3486c3e47d147d90a01
Issue introduced in 6.1.103 with commit 5839f59ff1dd4e35b9e767927931a039484839e1 and fixed in 6.1.124 with commit 5d336714db324bef84490c75dcc48b387ef0346e
Issue introduced in 6.6.44 with commit 5a041d25b67042cbe06a0fb292ee22fd1147e65c and fixed in 6.6.70 with commit a693b87692b4d7c50f4fc08a996678d60534a9da
Issue introduced in 6.11 with commit 79eecf631c14e7f4057186570ac20e2cfac3802e and fixed in 6.12.9 with commit cd8488fdc7116f6da277515647b167859d4f72b1
Issue introduced in 6.11 with commit 79eecf631c14e7f4057186570ac20e2cfac3802e and fixed in 6.13-rc6 with commit f91a5b8089389eb408501af2762f168c3aaa7b79
Issue introduced in 4.19.320 with commit 3dfd84aa72fa7329ed4a257c8f40e0c9aff4dc8f
Issue introduced in 6.10.3 with commit 66f23a7b5174b5d3e7111fd2d0d5a4f3faaa12e5
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2024-57901
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
include/linux/if_vlan.h
net/packet/af_packet.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/560cbdd26b510626f3f4f27d34c44dfd3dd3499d
https://git.kernel.org/stable/c/0d3fa6c3c9ca7aa255696150f5b759ac4a4974e1
https://git.kernel.org/stable/c/de4f8d477c67ec1d7c28f3486c3e47d147d90a01
https://git.kernel.org/stable/c/5d336714db324bef84490c75dcc48b387ef0346e
https://git.kernel.org/stable/c/a693b87692b4d7c50f4fc08a996678d60534a9da
https://git.kernel.org/stable/c/cd8488fdc7116f6da277515647b167859d4f72b1
https://git.kernel.org/stable/c/f91a5b8089389eb408501af2762f168c3aaa7b79
Powered by blists - more mailing lists