BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2023-52796High confidence

ipvlan: add ipvlan_route_v6_outbound() helper

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.25% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.6.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.64-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.6.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.6.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2023-52796 · CSAF 2.0 · revision 104 · interimSUSE Product Security TeamCVE-2023-52796
250 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Enterprise Storage 7.1
  • kernel-default-devel as component of SUSE Enterprise Storage 7.1
  • kernel-devel as component of SUSE Enterprise Storage 7.1
  • kernel-macros as component of SUSE Enterprise Storage 7.1
  • kernel-source as component of SUSE Enterprise Storage 7.1
  • reiserfs-kmp-default as component of SUSE Enterprise Storage 7.1
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: ipvlan: add ipvlan_route_v6_outbound() helper Inspired by syzbot reports using a stack of multiple ipvlan devices. Reduce stack size needed in ipvlan_process_v6_outbound() by moving the flowi6 struct used for the route lookup in an non inlined helper. ipvlan_route_v6_outbound() needs 120 bytes on the stack, immediately reclaimed. Also make sure ipvlan_process_v4_outbound() is not inlined. We might also have to lower MAX_NEST_DEV, because only syzbot uses setups with more than four stacked devices. BUG: TASK stack guard page was hit at ffffc9000e803ff8 (stack is ffffc9000e804000..ffffc9000e808000) stack guard page: 0000 [#1] SMP KASAN CPU: 0 PID: 13442 Comm: syz-executor.4 Not tainted 6.1.52-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023 RIP: 0010:kasan_check_range+0x4/0x2a0 mm/kasan/generic.c:188 Code: 48 01 c6 48 89 c7 e8 db 4e c1 03 31 c0 5d c3 cc 0f 0b eb 02 0f 0b b8 ea ff ff ff 5d c3 cc 00 00 cc cc 00 00 cc cc 55 48 89 e5 57 41 56 41 55 41 54 53 b0 01 48 85 f6 0f 84 a4 01 00 00 48 89 RSP: 0018:ffffc9000e804000 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff817e5bf2 RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff887c6568 RBP: ffffc9000e804000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff92001d0080c R13: dffffc0000000000 R14: ffffffff87e6b100 R15: 0000000000000000 FS: 00007fd0c55826c0(0000) GS:ffff8881f6800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffc9000e803ff8 CR3: 0000000170ef7000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: [ ] __kasan_check_read+0x11/0x20 mm/kasan/shadow.c:31 [ ] instrument_atomic_read include/linux/instrumented.h:72 [inline] [ ] _test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline] [ ] cpumask_test_cpu include/linux/cpumask.h:506 [inline] [ ] cpu_online include/linux/cpumask.h:1092 [inline] [ ] trace_lock_acquire include/trace/events/lock.h:24 [inline] [ ] lock_acquire+0xe2/0x590 kernel/locking/lockdep.c:5632 [ ] rcu_lock_acquire+0x2e/0x40 include/linux/rcupdate.h:306 [ ] rcu_read_lock include/linux/rcupdate.h:747 [inline] [ ] ip6_pol_route+0x15d/0x1440 net/ipv6/route.c:2221 [ ] ip6_pol_route_output+0x50/0x80 net/ipv6/route.c:2606 [ ] pol_lookup_func include/net/ip6_fib.h:584 [inline] [ ] fib6_rule_lookup+0x265/0x620 net/ipv6/fib6_rules.c:116 [ ] ip6_route_output_flags_noref+0x2d9/0x3a0 net/ipv6/route.c:2638 [ ] ip6_route_output_flags+0xca/0x340 net/ipv6/route.c:2651 [ ] ip6_route_output include/net/ip6_route.h:100 [inline] [ ] ipvlan_process_v6_outbound drivers/net/ipvlan/ipvlan_core.c:473 [inline] [ ] ipvlan_process_outbound drivers/net/ipvlan/ipvlan_core.c:529 [inline] [ ] ipvlan_xmit_mode_l3 drivers/net/ipvlan/ipvlan_core.c:602 [inline] [ ] ipvlan_queue_xmit+0xc33/0x1be0 drivers/net/ipvlan/ipvlan_core.c:677 [ ] ipvlan_start_xmit+0x49/0x100 drivers/net/ipvlan/ipvlan_main.c:229 [ ] netdev_start_xmit include/linux/netdevice.h:4966 [inline] [ ] xmit_one net/core/dev.c:3644 [inline] [ ] dev_hard_start_xmit+0x320/0x980 net/core/dev.c:3660 [ ] __dev_queue_xmit+0x16b2/0x3370 net/core/dev.c:4324 [ ] dev_queue_xmit include/linux/netdevice.h:3067 [inline] [ ] neigh_hh_output include/net/neighbour.h:529 [inline] [<f ---truncated---
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-613116 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-613116: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.1
3 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
  • SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
  • SCALANCE XCM-/XRM-/XCH-/XRH-300 family
Summary
In the Linux kernel, the following vulnerability has been resolved: ipvlan: add ipvlan_route_v6_outbound() helper
Remediation
No remediation text is recorded.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2023-59513

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: ipvlan: add ipvlan_route_v6_outbound() helper Inspired by syzbot reports using a stack of multiple ipvlan devices. Reduce stack size needed in ipvlan_process_v6_outbound() by moving the flowi6 struct used for the route lookup in an non inlined helper. ipvlan_route_v6_outbound() needs 120 bytes on the stack, immediately reclaimed. Also make sure ipvlan_process_v4_outbound() is not inlined. We might also have to lower MAX_NEST_DEV, because only syzbot uses setups with more than four stacked devices. BUG: TASK stack guard page was hit at ffffc9000e803ff8 (stack is ffffc9000e804000..ffffc9000e808000) stack guard page: 0000 [#1] SMP KASAN CPU: 0 PID: 13442 Comm: syz-executor.4 Not tainted 6.1.52-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023 RIP: 0010:kasan_check_range+0x4/0x2a0 mm/kasan/generic.c:188 Code: 48 01 c6 48 89 c7 e8 db 4e c1 03 31 c0 5d c3 cc 0f 0b eb 02 0f 0b b8 ea ff ff ff 5d c3 cc 00 00 cc cc 00 00 cc cc 55 48 89 e5 <41> 57 41 56 41 55 41 54 53 b0 01 48 85 f6 0f 84 a4 01 00 00 48 89 RSP: 0018:ffffc9000e804000 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff817e5bf2 RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff887c6568 RBP: ffffc9000e804000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff92001d0080c R13: dffffc0000000000 R14: ffffffff87e6b100 R15: 0000000000000000 FS: 00007fd0c55826c0(0000) GS:ffff8881f6800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffc9000e803ff8 CR3: 0000000170ef7000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <#DF> </#DF> <TASK> [<ffffffff81f281d1>] __kasan_check_read+0x11/0x20 mm/kasan/shadow.c:31 [<ffffffff817e5bf2>] instrument_atomic_read include/linux/instrumented.h:72 [inline] [<ffffffff817e5bf2>] _test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline] [<ffffffff817e5bf2>] cpumask_test_cpu include/linux/cpumask.h:506 [inline] [<ffffffff817e5bf2>] cpu_online include/linux/cpumask.h:1092 [inline] [<ffffffff817e5bf2>] trace_lock_acquire include/trace/events/lock.h:24 [inline] [<ffffffff817e5bf2>] lock_acquire+0xe2/0x590 kernel/locking/lockdep.c:5632 [<ffffffff8563221e>] rcu_lock_acquire+0x2e/0x40 include/linux/rcupdate.h:306 [<ffffffff8561464d>] rcu_read_lock include/linux/rcupdate.h:747 [inline] [<ffffffff8561464d>] ip6_pol_route+0x15d/0x1440 net/ipv6/route.c:2221 [<ffffffff85618120>] ip6_pol_route_output+0x50/0x80 net/ipv6/route.c:2606 [<ffffffff856f65b5>] pol_lookup_func include/net/ip6_fib.h:584 [inline] [<ffffffff856f65b5>] fib6_rule_lookup+0x265/0x620 net/ipv6/fib6_rules.c:116 [<ffffffff85618009>] ip6_route_output_flags_noref+0x2d9/0x3a0 net/ipv6/route.c:2638 [<ffffffff8561821a>] ip6_route_output_flags+0xca/0x340 net/ipv6/route.c:2651 [<ffffffff838bd5a3>] ip6_route_output include/net/ip6_route.h:100 [inline] [<ffffffff838bd5a3>] ipvlan_process_v6_outbound drivers/net/ipvlan/ipvlan_core.c:473 [inline] [<ffffffff838bd5a3>] ipvlan_process_outbound drivers/net/ipvlan/ipvlan_core.c:529 [inline] [<ffffffff838bd5a3>] ipvlan_xmit_mode_l3 drivers/net/ipvlan/ipvlan_core.c:602 [inline] [<ffffffff838bd5a3>] ipvlan_queue_xmit+0xc33/0x1be0 drivers/net/ipvlan/ipvlan_core.c:677 [<ffffffff838c2909>] ipvlan_start_xmit+0x49/0x100 drivers/net/ipvlan/ipvlan_main.c:229 [<ffffffff84d03900>] netdev_start_xmit include/linux/netdevice.h:4966 [inline] [<ffffffff84d03900>] xmit_one net/core/dev.c:3644 [inline] [<ffffffff84d03900>] dev_hard_start_xmit+0x320/0x980 net/core/dev.c:3660 [<ffffffff84d080e2>] __dev_queue_xmit+0x16b2/0x3370 net/core/dev.c:4324 [<ffffffff855ce4cd>] dev_queue_xmit include/linux/netdevice.h:3067 [inline] [<ffffffff855ce4cd>] neigh_hh_output include/net/neighbour.h:529 [inline] [<f ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: ipvlan: add ipvlan_route_v6_outbound() helper Inspired by syzbot reports using a stack of multiple ipvlan devices. Reduce stack size needed in ipvlan_process_v6_outbound() by moving the flowi6 struct used for the route lookup in an non inlined helper. ipvlan_route_v6_outbound() needs 120 bytes on the stack, immediately reclaimed. Also make sure ipvlan_process_v4_outbound() is not inlined. We might also have to lower MAX_NEST_DEV, because only syzbot uses setups with more than four stacked devices. BUG: TASK stack guard page was hit at ffffc9000e803ff8 (stack is ffffc9000e804000..ffffc9000e808000) stack guard page: 0000 [#1] SMP KASAN CPU: 0 PID: 13442 Comm: syz-executor.4 Not tainted 6.1.52-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023 RIP: 0010:kasan_check_range+0x4/0x2a0 mm/kasan/generic.c:188 Code: 48 01 c6 48 89 c7 e8 db 4e c1 03 31 c0 5d c3 cc 0f 0b eb 02 0f 0b b8 ea ff ff ff 5d c3 cc 00 00 cc cc 00 00 cc cc 55 48 89 e5 <41> 57 41 56 41 55 41 54 53 b0 01 48 85 f6 0f 84 a4 01 00 00 48 89 RSP: 0018:ffffc9000e804000 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff817e5bf2 RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff887c6568 RBP: ffffc9000e804000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff92001d0080c R13: dffffc0000000000 R14: ffffffff87e6b100 R15: 0000000000000000 FS: 00007fd0c55826c0(0000) GS:ffff8881f6800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffc9000e803ff8 CR3: 0000000170ef7000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <#DF> </#DF> <TASK> [<ffffffff81f281d1>] __kasan_check_read+0x11/0x20 mm/kasan/shadow.c:31 [<ffffffff817e5bf2>] instrument_atomic_read include/linux/instrumented.h:72 [inline] [<ffffffff817e5bf2>] _test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline] [<ffffffff817e5bf2>] cpumask_test_cpu include/linux/cpumask.h:506 [inline] [<ffffffff817e5bf2>] cpu_online include/linux/cpumask.h:1092 [inline] [<ffffffff817e5bf2>] trace_lock_acquire include/trace/events/lock.h:24 [inline] [<ffffffff817e5bf2>] lock_acquire+0xe2/0x590 kernel/locking/lockdep.c:5632 [<ffffffff8563221e>] rcu_lock_acquire+0x2e/0x40 include/linux/rcupdate.h:306 [<ffffffff8561464d>] rcu_read_lock include/linux/rcupdate.h:747 [inline] [<ffffffff8561464d>] ip6_pol_route+0x15d/0x1440 net/ipv6/route.c:2221 [<ffffffff85618120>] ip6_pol_route_output+0x50/0x80 net/ipv6/route.c:2606 [<ffffffff856f65b5>] pol_lookup_func include/net/ip6_fib.h:584 [inline] [<ffffffff856f65b5>] fib6_rule_lookup+0x265/0x620 net/ipv6/fib6_rules.c:116 [<ffffffff85618009>] ip6_route_output_flags_noref+0x2d9/0x3a0 net/ipv6/route.c:2638 [<ffffffff8561821a>] ip6_route_output_flags+0xca/0x340 net/ipv6/route.c:2651 [<ffffffff838bd5a3>] ip6_route_output include/net/ip6_route.h:100 [inline] [<ffffffff838bd5a3>] ipvlan_process_v6_outbound drivers/net/ipvlan/ipvlan_core.c:473 [inline] [<ffffffff838bd5a3>] ipvlan_process_outbound drivers/net/ipvlan/ipvlan_core.c:529 [inline] [<ffffffff838bd5a3>] ipvlan_xmit_mode_l3 drivers/net/ipvlan/ipvlan_core.c:602 [inline] [<ffffffff838bd5a3>] ipvlan_queue_xmit+0xc33/0x1be0 drivers/net/ipvlan/ipvlan_core.c:677 [<ffffffff838c2909>] ipvlan_start_xmit+0x49/0x100 drivers/net/ipvlan/ipvlan_main.c:229 [<ffffffff84d03900>] netdev_start_xmit include/linux/netdevice.h:4966 [inline] [<ffffffff84d03900>] xmit_one net/core/dev.c:3644 [inline] [<ffffffff84d03900>] dev_hard_start_xmit+0x320/0x980 net/core/dev.c:3660 [<ffffffff84d080e2>] __dev_queue_xmit+0x16b2/0x3370 net/core/dev.c:4324 [<ffffffff855ce4cd>] dev_queue_xmit include/linux/netdevice.h:3067 [inline] [<ffffffff855ce4cd>] neigh_hh_output include/net/neighbour.h:529 [inline] [<f ---truncated---

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: ipvlan: add ipvlan_route_v6_outbound() helper Inspired by syzbot reports using a stack of multiple ipvlan devices. Reduce stack size needed in ipvlan_process_v6_outbound() by moving the flowi6 struct used for the route lookup in an non inlined helper. ipvlan_route_v6_outbound() needs 120 bytes on the stack, immediately reclaimed. Also make sure ipvlan_process_v4_outbound() is not inlined. We might also have to lower MAX_NEST_DEV, because only syzbot uses setups with more than four stacked devices. BUG: TASK stack guard page was hit at ffffc9000e803ff8 (stack is ffffc9000e804000..ffffc9000e808000) stack guard page: 0000 [#1] SMP KASAN CPU: 0 PID: 13442 Comm: syz-executor.4 Not tainted 6.1.52-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023 RIP: 0010:kasan_check_range+0x4/0x2a0 mm/kasan/generic.c:188 Code: 48 01 c6 48 89 c7 e8 db 4e c1 03 31 c0 5d c3 cc 0f 0b eb 02 0f 0b b8 ea ff ff ff 5d c3 cc 00 00 cc cc 00 00 cc cc 55 48 89 e5 <41> 57 41 56 41 55 41 54 53 b0 01 48 85 f6 0f 84 a4 01 00 00 48 89 RSP: 0018:ffffc9000e804000 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff817e5bf2 RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff887c6568 RBP: ffffc9000e804000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff92001d0080c R13: dffffc0000000000 R14: ffffffff87e6b100 R15: 0000000000000000 FS: 00007fd0c55826c0(0000) GS:ffff8881f6800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffc9000e803ff8 CR3: 0000000170ef7000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <#DF> </#DF> <TASK> [<ffffffff81f281d1>] __kasan_check_read+0x11/0x20 mm/kasan/shadow.c:31 [<ffffffff817e5bf2>] instrument_atomic_read include/linux/instrumented.h:72 [inline] [<ffffffff817e5bf2>] _test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline] [<ffffffff817e5bf2>] cpumask_test_cpu include/linux/cpumask.h:506 [inline] [<ffffffff817e5bf2>] cpu_online include/linux/cpumask.h:1092 [inline] [<ffffffff817e5bf2>] trace_lock_acquire include/trace/events/lock.h:24 [inline] [<ffffffff817e5bf2>] lock_acquire+0xe2/0x590 kernel/locking/lockdep.c:5632 [<ffffffff8563221e>] rcu_lock_acquire+0x2e/0x40 include/linux/rcupdate.h:306 [<ffffffff8561464d>] rcu_read_lock include/linux/rcupdate.h:747 [inline] [<ffffffff8561464d>] ip6_pol_route+0x15d/0x1440 net/ipv6/route.c:2221 [<ffffffff85618120>] ip6_pol_route_output+0x50/0x80 net/ipv6/route.c:2606 [<ffffffff856f65b5>] pol_lookup_func include/net/ip6_fib.h:584 [inline] [<ffffffff856f65b5>] fib6_rule_lookup+0x265/0x620 net/ipv6/fib6_rules.c:116 [<ffffffff85618009>] ip6_route_output_flags_noref+0x2d9/0x3a0 net/ipv6/route.c:2638 [<ffffffff8561821a>] ip6_route_output_flags+0xca/0x340 net/ipv6/route.c:2651 [<ffffffff838bd5a3>] ip6_route_output include/net/ip6_route.h:100 [inline] [<ffffffff838bd5a3>] ipvlan_process_v6_outbound drivers/net/ipvlan/ipvlan_core.c:473 [inline] [<ffffffff838bd5a3>] ipvlan_process_outbound drivers/net/ipvlan/ipvlan_core.c:529 [inline] [<ffffffff838bd5a3>] ipvlan_xmit_mode_l3 drivers/net/ipvlan/ipvlan_core.c:602 [inline] [<ffffffff838bd5a3>] ipvlan_queue_xmit+0xc33/0x1be0 drivers/net/ipvlan/ipvlan_core.c:677 [<ffffffff838c2909>] ipvlan_start_xmit+0x49/0x100 drivers/net/ipvlan/ipvlan_main.c:229 [<ffffffff84d03900>] netdev_start_xmit include/linux/netdevice.h:4966 [inline] [<ffffffff84d03900>] xmit_one net/core/dev.c:3644 [inline] [<ffffffff84d03900>] dev_hard_start_xmit+0x320/0x980 net/core/dev.c:3660 [<ffffffff84d080e2>] __dev_queue_xmit+0x16b2/0x3370 net/core/dev.c:4324 [<ffffffff855ce4cd>] dev_queue_xmit include/linux/netdevice.h:3067 [inline] [<ffffffff855ce4cd>] neigh_hh_output include/net/neighbour.h:529 [inline] [<f ---truncated---

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Out-of-bounds Write → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-787 ↗

CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-787
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-1913Red Hat OpenShift Container Platform: Mehrere Schwachstellen

Ein entfernter anonymer oder lokaler Angreifer kann mehrere Schwachstellen in Red Hat OpenShift Container Platform ausnutzen, um seine Privilegien zu erhöhen, beliebigen Code auszuführen, einen Denial-of-Service-Zustand zu erzeugen, vertrauliche Informationen offenzulegen, Dateien und Daten zu manipulieren oder Sicherheitsmaßnahmen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2025-0225Dell PowerProtect Data Domain: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell PowerProtect Data Domain ausnutzen, um erhöhte Rechte zu erlangen, einen Denial-of-Service-Zustand herbeizuführen und einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-1197Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und unspezifische Angriffe

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder unspezifische Angriffe durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240522Security Bulletin 22 May 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 May 2024, published on 22 May 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

d?id=CVE-2023-52730 Référence CVE CVE-2023-52756 https://www.cve.org/CVERecord?id=CVE-2023-52756 Référence CVE CVE-2023-52762 https://www.cve.org/CVERecord?id=CVE-2023-52762 Référence CVE CVE-2023-52764 https://www.cve.org/CVERecord?id=CVE-2023-52764 Référence CVE CVE-2023-52775 https://www.cve.org/CVERecord?id=CVE-2023-52775 Référence CVE CVE-2023-52777 https://www.cve.org/CVERecord?id=CVE-2023-52777 Référence CVE CVE-2023-52781 https://www.cve.org/CVERecord?id=CVE-2023-52781 Référence CVE CVE-2023-52784 https://www.cve.org/CVERecord?id=CVE-2023-52784 Référence CVE CVE-2023-52791 https://www.cve.org/CVERecord?id=CVE-2023-52791 Référence CVE CVE-2023-52796 https://www.cve.org/CVERecord?id=CVE-2023-52796 Référence CVE CVE-2023-52798 https://www.cve.org/CVERecord?id=CVE-2023-52798 Référence CVE CVE-2023-52800 https://www.cve.org/CVERecord?id=CVE-2023-52800 Référence CVE CVE-2023-52803 https://www.cve.org/CVERecord?id=CVE-2023-52803 Référence CVE CVE-2023-52809 https://www.cve.org/CVERecord?id=CVE-2023-52809 Référence CVE CVE-2023-52811 https://www.cve.org/CVERecord?id=CVE-2023-52811 Référence CVE CVE-2023-52813 https://www.cve.org/CVERecord?id=CVE-2023-52813 Référence CVE CVE-2023-52817 https://www.cve.org/CVERecord?id=CVE-2023-52817 Référence CVE CVE-2023-52832 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1057Multiples vulnérabilités dans les produits VMware

d?id=CVE-2023-52781 Référence CVE CVE-2023-52782 https://www.cve.org/CVERecord?id=CVE-2023-52782 Référence CVE CVE-2023-52786 https://www.cve.org/CVERecord?id=CVE-2023-52786 Référence CVE CVE-2023-52787 https://www.cve.org/CVERecord?id=CVE-2023-52787 Référence CVE CVE-2023-52788 https://www.cve.org/CVERecord?id=CVE-2023-52788 Référence CVE CVE-2023-52791 https://www.cve.org/CVERecord?id=CVE-2023-52791 Référence CVE CVE-2023-52792 https://www.cve.org/CVERecord?id=CVE-2023-52792 Référence CVE CVE-2023-52794 https://www.cve.org/CVERecord?id=CVE-2023-52794 Référence CVE CVE-2023-52795 https://www.cve.org/CVERecord?id=CVE-2023-52795 Référence CVE CVE-2023-52796 https://www.cve.org/CVERecord?id=CVE-2023-52796 Référence CVE CVE-2023-52803 https://www.cve.org/CVERecord?id=CVE-2023-52803 Référence CVE CVE-2023-52806 https://www.cve.org/CVERecord?id=CVE-2023-52806 Référence CVE CVE-2023-52813 https://www.cve.org/CVERecord?id=CVE-2023-52813 Référence CVE CVE-2023-52814 https://www.cve.org/CVERecord?id=CVE-2023-52814 Référence CVE CVE-2023-52817 https://www.cve.org/CVERecord?id=CVE-2023-52817 Référence CVE CVE-2023-52818 https://www.cve.org/CVERecord?id=CVE-2023-52818 Référence CVE CVE-2023-52828 https://www.cve.org/CVERecord?id=CVE-2023-52828 Référence CVE CVE-2023-52833 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0677Multiples vulnérabilités dans les produits Siemens

d?id=CVE-2023-52654 Référence CVE CVE-2023-52655 https://www.cve.org/CVERecord?id=CVE-2023-52655 Référence CVE CVE-2023-52670 https://www.cve.org/CVERecord?id=CVE-2023-52670 Référence CVE CVE-2023-52753 https://www.cve.org/CVERecord?id=CVE-2023-52753 Référence CVE CVE-2023-52764 https://www.cve.org/CVERecord?id=CVE-2023-52764 Référence CVE CVE-2023-52774 https://www.cve.org/CVERecord?id=CVE-2023-52774 Référence CVE CVE-2023-52784 https://www.cve.org/CVERecord?id=CVE-2023-52784 Référence CVE CVE-2023-52789 https://www.cve.org/CVERecord?id=CVE-2023-52789 Référence CVE CVE-2023-52791 https://www.cve.org/CVERecord?id=CVE-2023-52791 Référence CVE CVE-2023-52796 https://www.cve.org/CVERecord?id=CVE-2023-52796 Référence CVE CVE-2023-52799 https://www.cve.org/CVERecord?id=CVE-2023-52799 Référence CVE CVE-2023-52804 https://www.cve.org/CVERecord?id=CVE-2023-52804 Référence CVE CVE-2023-52805 https://www.cve.org/CVERecord?id=CVE-2023-52805 Référence CVE CVE-2023-52806 https://www.cve.org/CVERecord?id=CVE-2023-52806 Référence CVE CVE-2023-52809 https://www.cve.org/CVERecord?id=CVE-2023-52809 Référence CVE CVE-2023-52810 https://www.cve.org/CVERecord?id=CVE-2023-52810 Référence CVE CVE-2023-52813 https://www.cve.org/CVERecord?id=CVE-2023-52813 Référence CVE CVE-2023-52817 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0958Multiples vulnérabilités dans les produits IBM

d?id=CVE-2023-52707 Référence CVE CVE-2023-52730 https://www.cve.org/CVERecord?id=CVE-2023-52730 Référence CVE CVE-2023-52756 https://www.cve.org/CVERecord?id=CVE-2023-52756 Référence CVE CVE-2023-52762 https://www.cve.org/CVERecord?id=CVE-2023-52762 Référence CVE CVE-2023-52764 https://www.cve.org/CVERecord?id=CVE-2023-52764 Référence CVE CVE-2023-52775 https://www.cve.org/CVERecord?id=CVE-2023-52775 Référence CVE CVE-2023-52777 https://www.cve.org/CVERecord?id=CVE-2023-52777 Référence CVE CVE-2023-52784 https://www.cve.org/CVERecord?id=CVE-2023-52784 Référence CVE CVE-2023-52791 https://www.cve.org/CVERecord?id=CVE-2023-52791 Référence CVE CVE-2023-52796 https://www.cve.org/CVERecord?id=CVE-2023-52796 Référence CVE CVE-2023-52803 https://www.cve.org/CVERecord?id=CVE-2023-52803 Référence CVE CVE-2023-52811 https://www.cve.org/CVERecord?id=CVE-2023-52811 Référence CVE CVE-2023-52817 https://www.cve.org/CVERecord?id=CVE-2023-52817 Référence CVE CVE-2023-52832 https://www.cve.org/CVERecord?id=CVE-2023-52832 Référence CVE CVE-2023-52834 https://www.cve.org/CVERecord?id=CVE-2023-52834 Référence CVE CVE-2023-52845 https://www.cve.org/CVERecord?id=CVE-2023-52845 Référence CVE CVE-2023-52847 https://www.cve.org/CVERecord?id=CVE-2023-52847 Référence CVE CVE-2023-52864 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0717Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-52784 Référence CVE CVE-2023-52786 https://www.cve.org/CVERecord?id=CVE-2023-52786 Référence CVE CVE-2023-52787 https://www.cve.org/CVERecord?id=CVE-2023-52787 Référence CVE CVE-2023-52788 https://www.cve.org/CVERecord?id=CVE-2023-52788 Référence CVE CVE-2023-52789 https://www.cve.org/CVERecord?id=CVE-2023-52789 Référence CVE CVE-2023-52791 https://www.cve.org/CVERecord?id=CVE-2023-52791 Référence CVE CVE-2023-52792 https://www.cve.org/CVERecord?id=CVE-2023-52792 Référence CVE CVE-2023-52794 https://www.cve.org/CVERecord?id=CVE-2023-52794 Référence CVE CVE-2023-52795 https://www.cve.org/CVERecord?id=CVE-2023-52795 Référence CVE CVE-2023-52796 https://www.cve.org/CVERecord?id=CVE-2023-52796 Référence CVE CVE-2023-52798 https://www.cve.org/CVERecord?id=CVE-2023-52798 Référence CVE CVE-2023-52799 https://www.cve.org/CVERecord?id=CVE-2023-52799 Référence CVE CVE-2023-52800 https://www.cve.org/CVERecord?id=CVE-2023-52800 Référence CVE CVE-2023-52801 https://www.cve.org/CVERecord?id=CVE-2023-52801 Référence CVE CVE-2023-52803 https://www.cve.org/CVERecord?id=CVE-2023-52803 Référence CVE CVE-2023-52804 https://www.cve.org/CVERecord?id=CVE-2023-52804 Référence CVE CVE-2023-52805 https://www.cve.org/CVERecord?id=CVE-2023-52805 Référence CVE CVE-2023-52806 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0693Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-52784 Référence CVE CVE-2023-52786 https://www.cve.org/CVERecord?id=CVE-2023-52786 Référence CVE CVE-2023-52787 https://www.cve.org/CVERecord?id=CVE-2023-52787 Référence CVE CVE-2023-52788 https://www.cve.org/CVERecord?id=CVE-2023-52788 Référence CVE CVE-2023-52789 https://www.cve.org/CVERecord?id=CVE-2023-52789 Référence CVE CVE-2023-52791 https://www.cve.org/CVERecord?id=CVE-2023-52791 Référence CVE CVE-2023-52792 https://www.cve.org/CVERecord?id=CVE-2023-52792 Référence CVE CVE-2023-52794 https://www.cve.org/CVERecord?id=CVE-2023-52794 Référence CVE CVE-2023-52795 https://www.cve.org/CVERecord?id=CVE-2023-52795 Référence CVE CVE-2023-52796 https://www.cve.org/CVERecord?id=CVE-2023-52796 Référence CVE CVE-2023-52798 https://www.cve.org/CVERecord?id=CVE-2023-52798 Référence CVE CVE-2023-52799 https://www.cve.org/CVERecord?id=CVE-2023-52799 Référence CVE CVE-2023-52800 https://www.cve.org/CVERecord?id=CVE-2023-52800 Référence CVE CVE-2023-52801 https://www.cve.org/CVERecord?id=CVE-2023-52801 Référence CVE CVE-2023-52803 https://www.cve.org/CVERecord?id=CVE-2023-52803 Référence CVE CVE-2023-52804 https://www.cve.org/CVERecord?id=CVE-2023-52804 Référence CVE CVE-2023-52805 https://www.cve.org/CVERecord?id=CVE-2023-52805 Référence CVE CVE-2023-52806 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0668Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2023-52707 Référence CVE CVE-2023-52730 https://www.cve.org/CVERecord?id=CVE-2023-52730 Référence CVE CVE-2023-52756 https://www.cve.org/CVERecord?id=CVE-2023-52756 Référence CVE CVE-2023-52762 https://www.cve.org/CVERecord?id=CVE-2023-52762 Référence CVE CVE-2023-52764 https://www.cve.org/CVERecord?id=CVE-2023-52764 Référence CVE CVE-2023-52775 https://www.cve.org/CVERecord?id=CVE-2023-52775 Référence CVE CVE-2023-52777 https://www.cve.org/CVERecord?id=CVE-2023-52777 Référence CVE CVE-2023-52784 https://www.cve.org/CVERecord?id=CVE-2023-52784 Référence CVE CVE-2023-52791 https://www.cve.org/CVERecord?id=CVE-2023-52791 Référence CVE CVE-2023-52796 https://www.cve.org/CVERecord?id=CVE-2023-52796 Référence CVE CVE-2023-52803 https://www.cve.org/CVERecord?id=CVE-2023-52803 Référence CVE CVE-2023-52809 https://www.cve.org/CVERecord?id=CVE-2023-52809 Référence CVE CVE-2023-52811 https://www.cve.org/CVERecord?id=CVE-2023-52811 Référence CVE CVE-2023-52832 https://www.cve.org/CVERecord?id=CVE-2023-52832 Référence CVE CVE-2023-52834 https://www.cve.org/CVERecord?id=CVE-2023-52834 Référence CVE CVE-2023-52845 https://www.cve.org/CVERecord?id=CVE-2023-52845 Référence CVE CVE-2023-52847 https://www.cve.org/CVERecord?id=CVE-2023-52847 Référence CVE CVE-2023-52864 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0632Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-52784 Référence CVE CVE-2023-52786 https://www.cve.org/CVERecord?id=CVE-2023-52786 Référence CVE CVE-2023-52787 https://www.cve.org/CVERecord?id=CVE-2023-52787 Référence CVE CVE-2023-52788 https://www.cve.org/CVERecord?id=CVE-2023-52788 Référence CVE CVE-2023-52789 https://www.cve.org/CVERecord?id=CVE-2023-52789 Référence CVE CVE-2023-52791 https://www.cve.org/CVERecord?id=CVE-2023-52791 Référence CVE CVE-2023-52792 https://www.cve.org/CVERecord?id=CVE-2023-52792 Référence CVE CVE-2023-52794 https://www.cve.org/CVERecord?id=CVE-2023-52794 Référence CVE CVE-2023-52795 https://www.cve.org/CVERecord?id=CVE-2023-52795 Référence CVE CVE-2023-52796 https://www.cve.org/CVERecord?id=CVE-2023-52796 Référence CVE CVE-2023-52798 https://www.cve.org/CVERecord?id=CVE-2023-52798 Référence CVE CVE-2023-52799 https://www.cve.org/CVERecord?id=CVE-2023-52799 Référence CVE CVE-2023-52800 https://www.cve.org/CVERecord?id=CVE-2023-52800 Référence CVE CVE-2023-52801 https://www.cve.org/CVERecord?id=CVE-2023-52801 Référence CVE CVE-2023-52803 https://www.cve.org/CVERecord?id=CVE-2023-52803 Référence CVE CVE-2023-52804 https://www.cve.org/CVERecord?id=CVE-2023-52804 Référence CVE CVE-2023-52805 https://www.cve.org/CVERecord?id=CVE-2023-52805 Référence CVE CVE-2023-52806 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0526Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-52772 Référence CVE CVE-2023-52773 https://www.cve.org/CVERecord?id=CVE-2023-52773 Référence CVE CVE-2023-52774 https://www.cve.org/CVERecord?id=CVE-2023-52774 Référence CVE CVE-2023-52777 https://www.cve.org/CVERecord?id=CVE-2023-52777 Référence CVE CVE-2023-52781 https://www.cve.org/CVERecord?id=CVE-2023-52781 Référence CVE CVE-2023-52788 https://www.cve.org/CVERecord?id=CVE-2023-52788 Référence CVE CVE-2023-52789 https://www.cve.org/CVERecord?id=CVE-2023-52789 Référence CVE CVE-2023-52791 https://www.cve.org/CVERecord?id=CVE-2023-52791 Référence CVE CVE-2023-52795 https://www.cve.org/CVERecord?id=CVE-2023-52795 Référence CVE CVE-2023-52796 https://www.cve.org/CVERecord?id=CVE-2023-52796 Référence CVE CVE-2023-52798 https://www.cve.org/CVERecord?id=CVE-2023-52798 Référence CVE CVE-2023-52799 https://www.cve.org/CVERecord?id=CVE-2023-52799 Référence CVE CVE-2023-52800 https://www.cve.org/CVERecord?id=CVE-2023-52800 Référence CVE CVE-2023-52803 https://www.cve.org/CVERecord?id=CVE-2023-52803 Référence CVE CVE-2023-52804 https://www.cve.org/CVERecord?id=CVE-2023-52804 Référence CVE CVE-2023-52805 https://www.cve.org/CVERecord?id=CVE-2023-52805 Référence CVE CVE-2023-52806 https://www.cve.org/CVERecord?id=CVE-2023-52806 Référence CVE CVE-2023-52807 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0496Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-52766 Référence CVE CVE-2023-52773 https://www.cve.org/CVERecord?id=CVE-2023-52773 Référence CVE CVE-2023-52774 https://www.cve.org/CVERecord?id=CVE-2023-52774 Référence CVE CVE-2023-52777 https://www.cve.org/CVERecord?id=CVE-2023-52777 Référence CVE CVE-2023-52781 https://www.cve.org/CVERecord?id=CVE-2023-52781 Référence CVE CVE-2023-52788 https://www.cve.org/CVERecord?id=CVE-2023-52788 Référence CVE CVE-2023-52789 https://www.cve.org/CVERecord?id=CVE-2023-52789 Référence CVE CVE-2023-52791 https://www.cve.org/CVERecord?id=CVE-2023-52791 Référence CVE CVE-2023-52795 https://www.cve.org/CVERecord?id=CVE-2023-52795 Référence CVE CVE-2023-52796 https://www.cve.org/CVERecord?id=CVE-2023-52796 Référence CVE CVE-2023-52798 https://www.cve.org/CVERecord?id=CVE-2023-52798 Référence CVE CVE-2023-52799 https://www.cve.org/CVERecord?id=CVE-2023-52799 Référence CVE CVE-2023-52800 https://www.cve.org/CVERecord?id=CVE-2023-52800 Référence CVE CVE-2023-52803 https://www.cve.org/CVERecord?id=CVE-2023-52803 Référence CVE CVE-2023-52804 https://www.cve.org/CVERecord?id=CVE-2023-52804 Référence CVE CVE-2023-52805 https://www.cve.org/CVERecord?id=CVE-2023-52805 Référence CVE CVE-2023-52806 https://www.cve.org/CVERecord?id=CVE-2023-52806 Référence CVE CVE-2023-52807 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-029815Linux の Linux Kernel における境界外書き込みに関する脆弱性

Linux の Linux Kernel には、境界外書き込みに関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 3.19, 4.19.300 ≤ 4.19.*, 5.4.262 ≤ 5.4.*, 5.10.202 ≤ 5.10.*, 5.15.140 ≤ 5.15.*, 6.1.64 ≤ 6.1.*, 6.5.13 ≤ 6.5.*, 6.6.3 ≤ 6.6.*, 6.7 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 21 May 2024 · Last source change 11 May 2026, 19:33 UTC · CWE-787 · Out-of-bounds Write

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2023-59513
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2023-59513↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2023-52796 · cve.blacktree.nl