GHSA-PW5G-24RM-MRGW
Vulnerability from github – Published: 2024-05-19 09:34 – Updated: 2025-03-21 18:31In the Linux kernel, the following vulnerability has been resolved:
mptcp: prevent BPF accessing lowat from a subflow socket.
Alexei reported the following splat:
WARNING: CPU: 32 PID: 3276 at net/mptcp/subflow.c:1430 subflow_data_ready+0x147/0x1c0 Modules linked in: dummy bpf_testmod(O) [last unloaded: bpf_test_no_cfi(O)] CPU: 32 PID: 3276 Comm: test_progs Tainted: GO 6.8.0-12873-g2c43c33bfd23 Call Trace: mptcp_set_rcvlowat+0x79/0x1d0 sk_setsockopt+0x6c0/0x1540 __bpf_setsockopt+0x6f/0x90 bpf_sock_ops_setsockopt+0x3c/0x90 bpf_prog_509ce5db2c7f9981_bpf_test_sockopt_int+0xb4/0x11b bpf_prog_dce07e362d941d2b_bpf_test_socket_sockopt+0x12b/0x132 bpf_prog_348c9b5faaf10092_skops_sockopt+0x954/0xe86 __cgroup_bpf_run_filter_sock_ops+0xbc/0x250 tcp_connect+0x879/0x1160 tcp_v6_connect+0x50c/0x870 mptcp_connect+0x129/0x280 __inet_stream_connect+0xce/0x370 inet_stream_connect+0x36/0x50 bpf_trampoline_6442491565+0x49/0xef inet_stream_connect+0x5/0x50 __sys_connect+0x63/0x90 __x64_sys_connect+0x14/0x20
The root cause of the issue is that bpf allows accessing mptcp-level proto_ops from a tcp subflow scope.
Fix the issue detecting the problematic call and preventing any action.
{
"affected": [],
"aliases": [
"CVE-2024-35894"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-05-19T09:15:10Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: prevent BPF accessing lowat from a subflow socket.\n\nAlexei reported the following splat:\n\n WARNING: CPU: 32 PID: 3276 at net/mptcp/subflow.c:1430 subflow_data_ready+0x147/0x1c0\n Modules linked in: dummy bpf_testmod(O) [last unloaded: bpf_test_no_cfi(O)]\n CPU: 32 PID: 3276 Comm: test_progs Tainted: GO 6.8.0-12873-g2c43c33bfd23\n Call Trace:\n \u003cTASK\u003e\n mptcp_set_rcvlowat+0x79/0x1d0\n sk_setsockopt+0x6c0/0x1540\n __bpf_setsockopt+0x6f/0x90\n bpf_sock_ops_setsockopt+0x3c/0x90\n bpf_prog_509ce5db2c7f9981_bpf_test_sockopt_int+0xb4/0x11b\n bpf_prog_dce07e362d941d2b_bpf_test_socket_sockopt+0x12b/0x132\n bpf_prog_348c9b5faaf10092_skops_sockopt+0x954/0xe86\n __cgroup_bpf_run_filter_sock_ops+0xbc/0x250\n tcp_connect+0x879/0x1160\n tcp_v6_connect+0x50c/0x870\n mptcp_connect+0x129/0x280\n __inet_stream_connect+0xce/0x370\n inet_stream_connect+0x36/0x50\n bpf_trampoline_6442491565+0x49/0xef\n inet_stream_connect+0x5/0x50\n __sys_connect+0x63/0x90\n __x64_sys_connect+0x14/0x20\n\nThe root cause of the issue is that bpf allows accessing mptcp-level\nproto_ops from a tcp subflow scope.\n\nFix the issue detecting the problematic call and preventing any action.",
"id": "GHSA-pw5g-24rm-mrgw",
"modified": "2025-03-21T18:31:29Z",
"published": "2024-05-19T09:34:47Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-35894"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3ffb1ab698376f09cc33101c07c1be229389fe29"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ee3c845787b621cfe82c2e52c513024a9d7a78f5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/fcf4692fa39e86a590c14a4af2de704e1d20a3b5"
},
{
"type": "WEB",
"url": "https://security.netapp.com/advisory/ntap-20250321-0002"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.