FKIE_CVE-2023-53831
Vulnerability from fkie_nvd - Published: 2025-12-09 16:17 - Updated: 2026-06-17 06:46| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"net/core/sock.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "7586a66b9c4f1b8a825ea1dfa3a91aad5cc7b89b",
"status": "affected",
"version": "7ad6848c7e81a603605fad3f3575841aab004eea",
"versionType": "git"
},
{
"lessThan": "e918d0211ffbaf039447334c3460cafee1ce0157",
"status": "affected",
"version": "7ad6848c7e81a603605fad3f3575841aab004eea",
"versionType": "git"
},
{
"lessThan": "41f10a4d78fe69d685a3172e6884297f233dcf95",
"status": "affected",
"version": "7ad6848c7e81a603605fad3f3575841aab004eea",
"versionType": "git"
},
{
"lessThan": "895dc4c47171a20035cdaa8d74c1c1e97f2fc974",
"status": "affected",
"version": "7ad6848c7e81a603605fad3f3575841aab004eea",
"versionType": "git"
},
{
"lessThan": "ed4e0adfa407ab65dd73b8862ebf2f308a0349d2",
"status": "affected",
"version": "7ad6848c7e81a603605fad3f3575841aab004eea",
"versionType": "git"
},
{
"lessThan": "9036b6342fcdab190d6edce3dd447859c1de90fc",
"status": "affected",
"version": "7ad6848c7e81a603605fad3f3575841aab004eea",
"versionType": "git"
},
{
"lessThan": "b1f5b890b89cb38a6c0bac91984d56cd69808e8c",
"status": "affected",
"version": "7ad6848c7e81a603605fad3f3575841aab004eea",
"versionType": "git"
},
{
"lessThan": "a3e0fdf71bbe031de845e8e08ed7fba49f9c702c",
"status": "affected",
"version": "7ad6848c7e81a603605fad3f3575841aab004eea",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"net/core/sock.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "2.6.33"
},
{
"lessThan": "2.6.33",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "4.14.*",
"status": "unaffected",
"version": "4.14.326",
"versionType": "semver"
},
{
"lessThanOrEqual": "4.19.*",
"status": "unaffected",
"version": "4.19.295",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.4.*",
"status": "unaffected",
"version": "5.4.257",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.195",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.132",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.54",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.5.*",
"status": "unaffected",
"version": "6.5.4",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.6",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: read sk-\u003esk_family once in sk_mc_loop()\n\nsyzbot is playing with IPV6_ADDRFORM quite a lot these days,\nand managed to hit the WARN_ON_ONCE(1) in sk_mc_loop()\n\nWe have many more similar issues to fix.\n\nWARNING: CPU: 1 PID: 1593 at net/core/sock.c:782 sk_mc_loop+0x165/0x260\nModules linked in:\nCPU: 1 PID: 1593 Comm: kworker/1:3 Not tainted 6.1.40-syzkaller #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023\nWorkqueue: events_power_efficient gc_worker\nRIP: 0010:sk_mc_loop+0x165/0x260 net/core/sock.c:782\nCode: 34 1b fd 49 81 c7 18 05 00 00 4c 89 f8 48 c1 e8 03 42 80 3c 20 00 74 08 4c 89 ff e8 25 36 6d fd 4d 8b 37 eb 13 e8 db 33 1b fd \u003c0f\u003e 0b b3 01 eb 34 e8 d0 33 1b fd 45 31 f6 49 83 c6 38 4c 89 f0 48\nRSP: 0018:ffffc90000388530 EFLAGS: 00010246\nRAX: ffffffff846d9b55 RBX: 0000000000000011 RCX: ffff88814f884980\nRDX: 0000000000000102 RSI: ffffffff87ae5160 RDI: 0000000000000011\nRBP: ffffc90000388550 R08: 0000000000000003 R09: ffffffff846d9a65\nR10: 0000000000000002 R11: ffff88814f884980 R12: dffffc0000000000\nR13: ffff88810dbee000 R14: 0000000000000010 R15: ffff888150084000\nFS: 0000000000000000(0000) GS:ffff8881f6b00000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000020000180 CR3: 000000014ee5b000 CR4: 00000000003506e0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n\u003cIRQ\u003e\n[\u003cffffffff8507734f\u003e] ip6_finish_output2+0x33f/0x1ae0 net/ipv6/ip6_output.c:83\n[\u003cffffffff85062766\u003e] __ip6_finish_output net/ipv6/ip6_output.c:200 [inline]\n[\u003cffffffff85062766\u003e] ip6_finish_output+0x6c6/0xb10 net/ipv6/ip6_output.c:211\n[\u003cffffffff85061f8c\u003e] NF_HOOK_COND include/linux/netfilter.h:298 [inline]\n[\u003cffffffff85061f8c\u003e] ip6_output+0x2bc/0x3d0 net/ipv6/ip6_output.c:232\n[\u003cffffffff852071cf\u003e] dst_output include/net/dst.h:444 [inline]\n[\u003cffffffff852071cf\u003e] ip6_local_out+0x10f/0x140 net/ipv6/output_core.c:161\n[\u003cffffffff83618fb4\u003e] ipvlan_process_v6_outbound drivers/net/ipvlan/ipvlan_core.c:483 [inline]\n[\u003cffffffff83618fb4\u003e] ipvlan_process_outbound drivers/net/ipvlan/ipvlan_core.c:529 [inline]\n[\u003cffffffff83618fb4\u003e] ipvlan_xmit_mode_l3 drivers/net/ipvlan/ipvlan_core.c:602 [inline]\n[\u003cffffffff83618fb4\u003e] ipvlan_queue_xmit+0x1174/0x1be0 drivers/net/ipvlan/ipvlan_core.c:677\n[\u003cffffffff8361ddd9\u003e] ipvlan_start_xmit+0x49/0x100 drivers/net/ipvlan/ipvlan_main.c:229\n[\u003cffffffff84763fc0\u003e] netdev_start_xmit include/linux/netdevice.h:4925 [inline]\n[\u003cffffffff84763fc0\u003e] xmit_one net/core/dev.c:3644 [inline]\n[\u003cffffffff84763fc0\u003e] dev_hard_start_xmit+0x320/0x980 net/core/dev.c:3660\n[\u003cffffffff8494c650\u003e] sch_direct_xmit+0x2a0/0x9c0 net/sched/sch_generic.c:342\n[\u003cffffffff8494d883\u003e] qdisc_restart net/sched/sch_generic.c:407 [inline]\n[\u003cffffffff8494d883\u003e] __qdisc_run+0xb13/0x1e70 net/sched/sch_generic.c:415\n[\u003cffffffff8478c426\u003e] qdisc_run+0xd6/0x260 include/net/pkt_sched.h:125\n[\u003cffffffff84796eac\u003e] net_tx_action+0x7ac/0x940 net/core/dev.c:5247\n[\u003cffffffff858002bd\u003e] __do_softirq+0x2bd/0x9bd kernel/softirq.c:599\n[\u003cffffffff814c3fe8\u003e] invoke_softirq kernel/softirq.c:430 [inline]\n[\u003cffffffff814c3fe8\u003e] __irq_exit_rcu+0xc8/0x170 kernel/softirq.c:683\n[\u003cffffffff814c3f09\u003e] irq_exit_rcu+0x9/0x20 kernel/softirq.c:695"
}
],
"id": "CVE-2023-53831",
"lastModified": "2026-06-17T06:46:08.910",
"metrics": {},
"published": "2025-12-09T16:17:22.017",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/41f10a4d78fe69d685a3172e6884297f233dcf95"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/7586a66b9c4f1b8a825ea1dfa3a91aad5cc7b89b"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/895dc4c47171a20035cdaa8d74c1c1e97f2fc974"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/9036b6342fcdab190d6edce3dd447859c1de90fc"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/a3e0fdf71bbe031de845e8e08ed7fba49f9c702c"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/b1f5b890b89cb38a6c0bac91984d56cd69808e8c"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/e918d0211ffbaf039447334c3460cafee1ce0157"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/ed4e0adfa407ab65dd73b8862ebf2f308a0349d2"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Deferred"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.