Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2023-52435 | First vendor Publication | 2024-02-20 |
Vendor | Cve | Last vendor Modification | 2024-11-21 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | |||
---|---|---|---|
Overall CVSS Score | 5.5 | ||
Base Score | 5.5 | Environmental Score | 5.5 |
impact SubScore | 3.6 | Temporal Score | 5.5 |
Exploitabality Sub Score | 1.8 | ||
Attack Vector | Local | Attack Complexity | Low |
Privileges Required | Low | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | None |
Integrity Impact | None | Availability Impact | High |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : | |||
---|---|---|---|
Cvss Base Score | N/A | Attack Range | N/A |
Cvss Impact Score | N/A | Attack Complexity | N/A |
Cvss Expoit Score | N/A | Authentication | N/A |
Calculate full CVSS 2.0 Vectors scores |
Detail
In the Linux kernel, the following vulnerability has been resolved: net: prevent mss overflow in skb_segment() Once again syzbot is able to crash the kernel in skb_segment() [1] GSO_BY_FRAGS is a forbidden value, but unfortunately the following computation in skb_segment() can reach it quite easily : mss = mss * partial_segs; 65535 = 3 * 5 * 17 * 257, so many initial values of mss can lead to a bad final result. Make sure to limit segmentation so that the new mss value is smaller than GSO_BY_FRAGS. [1] general protection fault, probably for non-canonical address 0xdffffc000000000e: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000070-0x0000000000000077] CPU: 1 PID: 5079 Comm: syz-executor993 Not tainted 6.7.0-rc4-syzkaller-00141-g1ae4cd3cbdd0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023 RIP: 0010:skb_segment+0x181d/0x3f30 net/core/skbuff.c:4551 Code: 83 e3 02 e9 fb ed ff ff e8 90 68 1c f9 48 8b 84 24 f8 00 00 00 48 8d 78 70 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <0f> b6 04 02 84 c0 74 08 3c 03 0f 8e 8a 21 00 00 48 8b 84 24 f8 00 RSP: 0018:ffffc900043473d0 EFLAGS: 00010202 RAX: dffffc0000000000 RBX: 0000000000010046 RCX: ffffffff886b1597 RDX: 000000000000000e RSI: ffffffff886b2520 RDI: 0000000000000070 RBP: ffffc90004347578 R08: 0000000000000005 R09: 000000000000ffff R10: 000000000000ffff R11: 0000000000000002 R12: ffff888063202ac0 R13: 0000000000010000 R14: 000000000000ffff R15: 0000000000000046 FS: 0000555556e7e380(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020010000 CR3: 0000000027ee2000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-52435 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-119 | Failure to Constrain Operations within the Bounds of a Memory Buffer |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-07-15 02:26:07 |
|
2025-07-14 12:28:18 |
|
2025-06-26 02:24:00 |
|
2025-06-25 12:26:58 |
|
2025-06-24 02:28:38 |
|
2025-05-27 13:38:43 |
|
2025-05-27 02:26:42 |
|
2025-03-29 03:29:52 |
|
2025-03-28 13:39:01 |
|
2025-03-28 03:09:59 |
|
2025-03-19 03:05:51 |
|
2025-03-18 03:18:20 |
|
2025-03-14 03:06:17 |
|
2025-02-22 03:16:12 |
|
2025-01-08 02:59:10 |
|
2025-01-07 02:58:47 |
|
2024-12-25 02:57:33 |
|
2024-12-12 03:00:42 |
|
2024-11-25 09:26:58 |
|
2024-11-21 21:24:40 |
|
2024-11-20 02:54:51 |
|
2024-11-14 02:55:00 |
|
2024-11-09 02:55:16 |
|
2024-10-26 02:52:40 |
|
2024-10-25 02:54:37 |
|
2024-10-23 02:53:55 |
|
2024-10-03 02:49:32 |
|
2024-10-02 02:47:56 |
|
2024-09-15 02:45:56 |
|
2024-09-11 21:28:08 |
|
2024-09-04 17:27:43 |
|
2024-09-04 02:47:03 |
|
2024-08-22 02:45:09 |
|
2024-08-02 13:54:07 |
|
2024-08-02 01:34:29 |
|
2024-06-26 05:27:38 |
|
2024-03-15 17:27:37 |
|
2024-02-23 13:27:24 |
|
2024-02-21 05:27:23 |
|