BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-45839High confidence

bpf: reject negative CO-RE accessor indices in bpf_core_parse_spec()

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 20 structured product or package states 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 27 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.18% 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 20 structured product or package states 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.

24 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 20 affected package states 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.12.94-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.10-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.10-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, 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
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
Ubuntu 24.04 LTSnoble · standard archivelinux-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
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, 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.

1 current
CVE-2026-45839 · CSAF 2.0 · revision 12 · interimSUSE Product Security TeamCVE-2026-45839
201 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP3
Summary
In the Linux kernel, the following vulnerability has been resolved: bpf: reject negative CO-RE accessor indices in bpf_core_parse_spec() CO-RE accessor strings are colon-separated indices that describe a path from a root BTF type to a target field, e.g. "0:1:2" walks through nested struct members. bpf_core_parse_spec() parses each component with sscanf("%d"), so negative values like -1 are silently accepted. The subsequent bounds checks (access_idx >= btf_vlen(t)) only guard the upper bound and always pass for negative values because C integer promotion converts the __u16 btf_vlen result to int, making the comparison (int)(-1) >= (int)(N) false for any positive N. When -1 reaches btf_member_bit_offset() it gets cast to u32 0xffffffff, producing an out-of-bounds read far past the members array. A crafted BPF program with a negative CO-RE accessor on any struct that exists in vmlinux BTF (e.g. task_struct) crashes the kernel deterministically during BPF_PROG_LOAD on any system with CONFIG_DEBUG_INFO_BTF=y (default on major distributions). The bug is reachable with CAP_BPF: BUG: unable to handle page fault for address: ffffed11818b6626 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP KASAN NOPTI CPU: 0 UID: 0 PID: 85 Comm: poc Not tainted 7.0.0-rc6 #18 PREEMPT(full) RIP: 0010:bpf_core_parse_spec (tools/lib/bpf/relo_core.c:354) RAX: 00000000ffffffff Call Trace: bpf_core_calc_relo_insn (tools/lib/bpf/relo_core.c:1321) bpf_core_apply (kernel/bpf/btf.c:9507) check_core_relo (kernel/bpf/verifier.c:19475) bpf_check (kernel/bpf/verifier.c:26031) bpf_prog_load (kernel/bpf/syscall.c:3089) __sys_bpf (kernel/bpf/syscall.c:6228) CO-RE accessor indices are inherently non-negative (struct member index, array element index, or enumerator index), so reject them immediately after parsing.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-2026-32165

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: bpf: reject negative CO-RE accessor indices in bpf_core_parse_spec() CO-RE accessor strings are colon-separated indices that describe a path from a root BTF type to a target field, e.g. "0:1:2" walks through nested struct members. bpf_core_parse_spec() parses each component with sscanf("%d"), so negative values like -1 are silently accepted. The subsequent bounds checks (access_idx >= btf_vlen(t)) only guard the upper bound and always pass for negative values because C integer promotion converts the __u16 btf_vlen result to int, making the comparison (int)(-1) >= (int)(N) false for any positive N. When -1 reaches btf_member_bit_offset() it gets cast to u32 0xffffffff, producing an out-of-bounds read far past the members array. A crafted BPF program with a negative CO-RE accessor on any struct that exists in vmlinux BTF (e.g. task_struct) crashes the kernel deterministically during BPF_PROG_LOAD on any system with CONFIG_DEBUG_INFO_BTF=y (default on major distributions). The bug is reachable with CAP_BPF: BUG: unable to handle page fault for address: ffffed11818b6626 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP KASAN NOPTI CPU: 0 UID: 0 PID: 85 Comm: poc Not tainted 7.0.0-rc6 #18 PREEMPT(full) RIP: 0010:bpf_core_parse_spec (tools/lib/bpf/relo_core.c:354) RAX: 00000000ffffffff Call Trace: <TASK> bpf_core_calc_relo_insn (tools/lib/bpf/relo_core.c:1321) bpf_core_apply (kernel/bpf/btf.c:9507) check_core_relo (kernel/bpf/verifier.c:19475) bpf_check (kernel/bpf/verifier.c:26031) bpf_prog_load (kernel/bpf/syscall.c:3089) __sys_bpf (kernel/bpf/syscall.c:6228) </TASK> CO-RE accessor indices are inherently non-negative (struct member index, array element index, or enumerator index), so reject them immediately after parsing.

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
0.0
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 20 structured product or package states 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: bpf: reject negative CO-RE accessor indices in bpf_core_parse_spec() CO-RE accessor strings are colon-separated indices that describe a path from a root BTF type to a target field, e.g. "0:1:2" walks through nested struct members. bpf_core_parse_spec() parses each component with sscanf("%d"), so negative values like -1 are silently accepted. The subsequent bounds checks (access_idx >= btf_vlen(t)) only guard the upper bound and always pass for negative values because C integer promotion converts the __u16 btf_vlen result to int, making the comparison (int)(-1) >= (int)(N) false for any positive N. When -1 reaches btf_member_bit_offset() it gets cast to u32 0xffffffff, producing an out-of-bounds read far past the members array. A crafted BPF program with a negative CO-RE accessor on any struct that exists in vmlinux BTF (e.g. task_struct) crashes the kernel deterministically during BPF_PROG_LOAD on any system with CONFIG_DEBUG_INFO_BTF=y (default on major distributions). The bug is reachable with CAP_BPF: BUG: unable to handle page fault for address: ffffed11818b6626 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP KASAN NOPTI CPU: 0 UID: 0 PID: 85 Comm: poc Not tainted 7.0.0-rc6 #18 PREEMPT(full) RIP: 0010:bpf_core_parse_spec (tools/lib/bpf/relo_core.c:354) RAX: 00000000ffffffff Call Trace: <TASK> bpf_core_calc_relo_insn (tools/lib/bpf/relo_core.c:1321) bpf_core_apply (kernel/bpf/btf.c:9507) check_core_relo (kernel/bpf/verifier.c:19475) bpf_check (kernel/bpf/verifier.c:26031) bpf_prog_load (kernel/bpf/syscall.c:3089) __sys_bpf (kernel/bpf/syscall.c:6228) </TASK> CO-RE accessor indices are inherently non-negative (struct member index, array element index, or enumerator index), so reject them immediately after parsing.

What

In the Linux kernel, the following vulnerability has been resolved: bpf: reject negative CO-RE accessor indices in bpf_core_parse_spec() CO-RE accessor strings are colon-separated indices that describe a path from a root BTF type to a target field, e.g. "0:1:2" walks through nested struct members. bpf_core_parse_spec() parses each component with sscanf("%d"), so negative values like -1 are silently accepted. The subsequent bounds checks (access_idx >= btf_vlen(t)) only guard the upper bound and always pass for negative values because C integer promotion converts the __u16 btf_vlen result to int, making the comparison (int)(-1) >= (int)(N) false for any positive N. When -1 reaches btf_member_bit_offset() it gets cast to u32 0xffffffff, producing an out-of-bounds read far past the members array. A crafted BPF program with a negative CO-RE accessor on any struct that exists in vmlinux BTF (e.g. task_struct) crashes the kernel deterministically during BPF_PROG_LOAD on any system with CONFIG_DEBUG_INFO_BTF=y (default on major distributions). The bug is reachable with CAP_BPF: BUG: unable to handle page fault for address: ffffed11818b6626 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP KASAN NOPTI CPU: 0 UID: 0 PID: 85 Comm: poc Not tainted 7.0.0-rc6 #18 PREEMPT(full) RIP: 0010:bpf_core_parse_spec (tools/lib/bpf/relo_core.c:354) RAX: 00000000ffffffff Call Trace: <TASK> bpf_core_calc_relo_insn (tools/lib/bpf/relo_core.c:1321) bpf_core_apply (kernel/bpf/btf.c:9507) check_core_relo (kernel/bpf/verifier.c:19475) bpf_check (kernel/bpf/verifier.c:26031) bpf_prog_load (kernel/bpf/syscall.c:3089) __sys_bpf (kernel/bpf/syscall.c:6228) </TASK> CO-RE accessor indices are inherently non-negative (struct member index, array element index, or enumerator index), so reject them immediately after parsing.

Why

The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: bpf: reject negative CO-RE accessor indices in bpf_core_parse_spec() CO-RE accessor strings are colon-separated indices that describe a path from a root BTF type to a target field, e.g. "0:1:2" walks through nested struct members. bpf_core_parse_spec() parses each component with sscanf("%d"), so negative values like -1 are silently accepted. The subsequent bounds checks (access_idx >= btf_vlen(t)) only guard the upper bound and always pass for negative values because C integer promotion converts the __u16 btf_vlen result to int, making the comparison (int)(-1) >= (int)(N) false for any positive N. When -1 reaches btf_member_bit_offset() it gets cast to u32 0xffffffff, producing an out-of-bounds read far past the members array. A crafted BPF program with a negative CO-RE accessor on any struct that exists in vmlinux BTF (e.g. task_struct) crashes the kernel deterministically during BPF_PROG_LOAD on any system with CONFIG_DEBUG_INFO_BTF=y (default on major distributions). The bug is reachable with CAP_BPF: BUG: unable to handle page fault for address: ffffed11818b6626 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP KASAN NOPTI CPU: 0 UID: 0 PID: 85 Comm: poc Not tainted 7.0.0-rc6 #18 PREEMPT(full) RIP: 0010:bpf_core_parse_spec (tools/lib/bpf/relo_core.c:354) RAX: 00000000ffffffff Call Trace: <TASK> bpf_core_calc_relo_insn (tools/lib/bpf/relo_core.c:1321) bpf_core_apply (kernel/bpf/btf.c:9507) check_core_relo (kernel/bpf/verifier.c:19475) bpf_check (kernel/bpf/verifier.c:26031) bpf_prog_load (kernel/bpf/syscall.c:3089) __sys_bpf (kernel/bpf/syscall.c:6228) </TASK> CO-RE accessor indices are inherently non-negative (struct member index, array element index, or enumerator index), so reject them immediately after parsing.

Why

The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

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 → Improper Validation of Array Index → disrupt the affected service
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-129 ↗

CWE-129: Improper Validation of Array Index. The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.

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.
Denial of serviceCWE-129
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-32165Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: bpf: reject negative CO-RE accessor indices in bpf_core_parse_spec() CO-RE accessor strings are colon-separated indices that describe a path from a root BTF type to a target field, e.g. "0:1:2" walks through nested struct members. bpf_core_parse_spec() parses each component with sscanf("%d"), so negative values like -1 are silently accepted. The subsequent bounds checks (access_idx >= btf_vlen(t)) only guard the upper bound and always pass for negative values because C integer promotion converts the __u16 btf_vlen result to int, making the comparison (int)(-1) >= (int)(N) false for any positive N. When -1 reaches btf_member_bit_offset() it gets cast to u32 0xffffffff, producing an out-of-bounds read far past the members array. A crafted BPF program with a negative CO-RE accessor on any struct that exists in vmlinux BTF (e.g. task_struct) crashes the kernel deterministically during BPF_PROG_LOAD on any system with CONFIG_DEBUG_INFO_BTF=y (default on major distributions). The bug is reachable with CAP_BPF: BUG: unable to handle page fault for address: ffffed11818b6626 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP KASAN NOPTI CPU: 0 UID: 0 PID: 85 Comm: poc Not tainted 7.0.0-rc6 #18 PREEMPT(full) RIP: 0010:bpf_core_parse_spec (tools/lib/bpf/relo_core.c:354) RAX: 00000000ffffffff Call Trace: <TASK> bpf_core_calc_relo_insn (tools/lib/bpf/relo_core.c:1321) bpf_core_apply (kernel/bpf/btf.c:9507) check_core_relo (kernel/bpf/verifier.c:19475) bpf_check (kernel/bpf/verifier.c:26031) bpf_prog_load (kernel/bpf/syscall.c:3089) __sys_bpf (kernel/bpf/syscall.c:6228) </TASK> CO-RE accessor indices are inherently non-negative (struct member index, array element index, or enumerator index), so reject them immediately after parsing.

Official EUVD record ↗
BSI · German · WID-SEC-2026-1691Linux Kernel: Mehrere Schwachstellen

Ein entfernter Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Zustand oder andere Auswirkungen herbeizuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260603Security Bulletin 3 Jun 2026

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

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43498 https://www.cve.org/CVERecord?id=CVE-2026-43498 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 Référence CVE CVE-2026-45838 https://www.cve.org/CVERecord?id=CVE-2026-45838 Référence CVE CVE-2026-45839 https://www.cve.org/CVERecord?id=CVE-2026-45839 Référence CVE CVE-2026-45840 https://www.cve.org/CVERecord?id=CVE-2026-45840 Référence CVE CVE-2026-45841 https://www.cve.org/CVERecord?id=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45844 https://www.cve.org/CVERecord?id=CVE-2026-45844 Référence CVE CVE-2026-45845 https://www.cve.org/CVERecord?id=CVE-2026-45845 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=CVE-2026-45846 Référence CVE CVE-2026-46104 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43497 Référence CVE CVE-2026-43498 https://www.cve.org/CVERecord?id=CVE-2026-43498 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 Référence CVE CVE-2026-45838 https://www.cve.org/CVERecord?id=CVE-2026-45838 Référence CVE CVE-2026-45839 https://www.cve.org/CVERecord?id=CVE-2026-45839 Référence CVE CVE-2026-45840 https://www.cve.org/CVERecord?id=CVE-2026-45840 Référence CVE CVE-2026-45841 https://www.cve.org/CVERecord?id=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45844 https://www.cve.org/CVERecord?id=CVE-2026-45844 Référence CVE CVE-2026-45845 https://www.cve.org/CVERecord?id=CVE-2026-45845 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=CVE-2026-45846 Référence CVE CVE-2026-45847 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43498 https://www.cve.org/CVERecord?id=CVE-2026-43498 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 Référence CVE CVE-2026-45838 https://www.cve.org/CVERecord?id=CVE-2026-45838 Référence CVE CVE-2026-45839 https://www.cve.org/CVERecord?id=CVE-2026-45839 Référence CVE CVE-2026-45840 https://www.cve.org/CVERecord?id=CVE-2026-45840 Référence CVE CVE-2026-45841 https://www.cve.org/CVERecord?id=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45844 https://www.cve.org/CVERecord?id=CVE-2026-45844 Référence CVE CVE-2026-45845 https://www.cve.org/CVERecord?id=CVE-2026-45845 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=CVE-2026-45846 Référence CVE CVE-2026-46104 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1093Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45838 https://www.cve.org/CVERecord?id=CVE-2026-45838 Référence CVE CVE-2026-45839 https://www.cve.org/CVERecord?id=CVE-2026-45839 Référence CVE CVE-2026-45840 https://www.cve.org/CVERecord?id=CVE-2026-45840 Référence CVE CVE-2026-45841 https://www.cve.org/CVERecord?id=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45844 https://www.cve.org/CVERecord?id=CVE-2026-45844 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=CVE-2026-45846 Référence CVE CVE-2026-45847 https://www.cve.org/CVERecord?id=CVE-2026-45847 Référence CVE CVE-2026-45848 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43497 Référence CVE CVE-2026-43498 https://www.cve.org/CVERecord?id=CVE-2026-43498 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 Référence CVE CVE-2026-45838 https://www.cve.org/CVERecord?id=CVE-2026-45838 Référence CVE CVE-2026-45839 https://www.cve.org/CVERecord?id=CVE-2026-45839 Référence CVE CVE-2026-45840 https://www.cve.org/CVERecord?id=CVE-2026-45840 Référence CVE CVE-2026-45841 https://www.cve.org/CVERecord?id=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45844 https://www.cve.org/CVERecord?id=CVE-2026-45844 Référence CVE CVE-2026-45845 https://www.cve.org/CVERecord?id=CVE-2026-45845 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=CVE-2026-45846 Référence CVE CVE-2026-45855 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43486 Référence CVE CVE-2026-43487 https://www.cve.org/CVERecord?id=CVE-2026-43487 Référence CVE CVE-2026-43488 https://www.cve.org/CVERecord?id=CVE-2026-43488 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43495 https://www.cve.org/CVERecord?id=CVE-2026-43495 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45839 https://www.cve.org/CVERecord?id=CVE-2026-45839 Référence CVE CVE-2026-45845 https://www.cve.org/CVERecord?id=CVE-2026-45845 Référence CVE CVE-2026-45849 https://www.cve.org/CVERecord?id=CVE-2026-45849 Référence CVE CVE-2026-45851 https://www.cve.org/CVERecord?id=CVE-2026-45851 Référence CVE CVE-2026-45853 https://www.cve.org/CVERecord?id=CVE-2026-45853 Référence CVE CVE-2026-45859 https://www.cve.org/CVERecord?id=CVE-2026-45859 Référence CVE CVE-2026-45863 https://www.cve.org/CVERecord?id=CVE-2026-45863 Référence CVE CVE-2026-45865 https://www.cve.org/CVERecord?id=CVE-2026-45865 Référence CVE CVE-2026-45866 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0985Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43480 Référence CVE CVE-2026-43484 https://www.cve.org/CVERecord?id=CVE-2026-43484 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45838 https://www.cve.org/CVERecord?id=CVE-2026-45838 Référence CVE CVE-2026-45839 https://www.cve.org/CVERecord?id=CVE-2026-45839 Référence CVE CVE-2026-45840 https://www.cve.org/CVERecord?id=CVE-2026-45840 Référence CVE CVE-2026-45841 https://www.cve.org/CVERecord?id=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45844 https://www.cve.org/CVERecord?id=CVE-2026-45844 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=CVE-2026-45846 Référence CVE CVE-2026-45847 https://www.cve.org/CVERecord?id=CVE-2026-45847 Référence CVE CVE-2026-45848 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43500 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 Référence CVE CVE-2026-45838 https://www.cve.org/CVERecord?id=CVE-2026-45838 Référence CVE CVE-2026-45839 https://www.cve.org/CVERecord?id=CVE-2026-45839 Référence CVE CVE-2026-45840 https://www.cve.org/CVERecord?id=CVE-2026-45840 Référence CVE CVE-2026-45841 https://www.cve.org/CVERecord?id=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45844 https://www.cve.org/CVERecord?id=CVE-2026-45844 Référence CVE CVE-2026-45845 https://www.cve.org/CVERecord?id=CVE-2026-45845 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=CVE-2026-45846 Référence CVE CVE-2026-45847 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43494 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 Référence CVE CVE-2026-45838 https://www.cve.org/CVERecord?id=CVE-2026-45838 Référence CVE CVE-2026-45839 https://www.cve.org/CVERecord?id=CVE-2026-45839 Référence CVE CVE-2026-45840 https://www.cve.org/CVERecord?id=CVE-2026-45840 Référence CVE CVE-2026-45841 https://www.cve.org/CVERecord?id=CVE-2026-45841 Référence CVE CVE-2026-45848 https://www.cve.org/CVERecord?id=CVE-2026-45848 Référence CVE CVE-2026-45851 https://www.cve.org/CVERecord?id=CVE-2026-45851 Référence CVE CVE-2026-45853 https://www.cve.org/CVERecord?id=CVE-2026-45853 Référence CVE CVE-2026-45857 https://www.cve.org/CVERecord?id=CVE-2026-45857 Référence CVE CVE-2026-45858 https://www.cve.org/CVERecord?id=CVE-2026-45858 Référence CVE CVE-2026-45861 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43500 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 Référence CVE CVE-2026-45838 https://www.cve.org/CVERecord?id=CVE-2026-45838 Référence CVE CVE-2026-45839 https://www.cve.org/CVERecord?id=CVE-2026-45839 Référence CVE CVE-2026-45840 https://www.cve.org/CVERecord?id=CVE-2026-45840 Référence CVE CVE-2026-45841 https://www.cve.org/CVERecord?id=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45844 https://www.cve.org/CVERecord?id=CVE-2026-45844 Référence CVE CVE-2026-45845 https://www.cve.org/CVERecord?id=CVE-2026-45845 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=CVE-2026-45846 Référence CVE CVE-2026-45847 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0862Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45838 https://www.cve.org/CVERecord?id=CVE-2026-45838 Référence CVE CVE-2026-45839 https://www.cve.org/CVERecord?id=CVE-2026-45839 Référence CVE CVE-2026-45840 https://www.cve.org/CVERecord?id=CVE-2026-45840 Référence CVE CVE-2026-45841 https://www.cve.org/CVERecord?id=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45844 https://www.cve.org/CVERecord?id=CVE-2026-45844 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=CVE-2026-45846 Référence CVE CVE-2026-45850 https://www.cve.org/CVERecord?id=CVE-2026-45850 Référence CVE CVE-2026-45930 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0809Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2026-31613 Référence CVE CVE-2026-31663 https://www.cve.org/CVERecord?id=CVE-2026-31663 Référence CVE CVE-2026-31717 https://www.cve.org/CVERecord?id=CVE-2026-31717 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43219 https://www.cve.org/CVERecord?id=CVE-2026-43219 Référence CVE CVE-2026-43245 https://www.cve.org/CVERecord?id=CVE-2026-43245 Référence CVE CVE-2026-43303 https://www.cve.org/CVERecord?id=CVE-2026-43303 Référence CVE CVE-2026-43331 https://www.cve.org/CVERecord?id=CVE-2026-43331 Référence CVE CVE-2026-45838 https://www.cve.org/CVERecord?id=CVE-2026-45838 Référence CVE CVE-2026-45839 https://www.cve.org/CVERecord?id=CVE-2026-45839 Référence CVE CVE-2026-45840 https://www.cve.org/CVERecord?id=CVE-2026-45840 Référence CVE CVE-2026-45841 https://www.cve.org/CVERecord?id=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45844 https://www.cve.org/CVERecord?id=CVE-2026-45844 Référence CVE CVE-2026-45845 https://www.cve.org/CVERecord?id=CVE-2026-45845 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=CVE-2026-45846 Référence CVE CVE-2026-45850 https://www.cve.org/CVERecord?id=

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

document Référence CERTFR-2026-AVI-0731 Titre Multiples vulnérabilités dans les produits Microsoft Date de la première version 10 juin 2026 Date de la dernière version 10 juin 2026 Source(s) Bulletin de sécurité Microsoft CVE-2026-39833 du 27 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43503 du 27 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46300 du 27 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45834 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45835 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45836 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45838 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45839 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45840 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45841 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45842 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45843 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45844 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45845 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45846 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45986 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45987 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45988 du 28 mai 2026 Bulletin de sécurité Mic

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-021338LinuxのLinux Kernelにおける配列インデックスの検証に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。bpf_core_parse_spec()関数内で負のCO-REアクセサインデックスを拒否します。CO-REアクセサ文字列はコロン区切りのインデックスで、ルートBTFタイプから対象フィールドへのパスを示します。例えば「0:1:2」はネストされた構造体メンバーを辿ります。bpf_core_parse_spec()は各コンポーネントをsscanf("%d")で解析するため、-1のような負の値が黙って受け入れられてしまいます。後続の境界チェック(access_idx = btf_vlen(t))は上限のみを監視しており、Cの整数昇格により__u16型のbtf_vlen結果がintに変換されるので、負の値は常に通過してしまいます。-1がbtf_member_bit_offset()に渡るとu32の0xffffffffにキャストされ、メンバー配列の範囲外読み込みが発生します。悪意を持って作成されたBPFプログラムがvmlinux BTFに存在する任意の構造体（例: task_struct）に負のCO-REアクセサを含む場合、CONFIG_DEBUG_INFO_BTF=y（主要ディストリビューションのデフォルト）な任意のシステムでBPF_PROG_LOAD中にカーネルが確実にクラッシュします。この脆弱性はCAP_BPF権限がある環境で到達可能です。エラー例：BUG: unable to handle page fault for address: ffffed11818b6626 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP KASAN NOPTI CPU: 0 UID: 0 PID: 85 Comm: poc Not tainted 7.0.0-rc6 #18 PREEMPT(full) RIP: 0010:bpf_core_parse_spec (tools/lib/bpf/relo_core.c:354) RAX: 00000000ffffffff Call Trace: TASK bpf_core_calc_relo_insn (tools/lib/bpf/relo_core.c:1321) bpf_core_apply (kernel/bpf/btf.c:9507) check_core_relo (kernel/bpf/verifier.c:19475) bpf_check (kernel/bpf/verifier.c:26031) bpf_prog_load (kernel/bpf/syscall.c:3089) __sys_bpf (kernel/bpf/syscall.c:6228) /TASKCO-REアクセサのインデックスは本質的に非負（構造体メンバーインデックス、配列要素インデックス、列挙子インデックス）であるため、解析直後にそれらを拒否します。

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: < 5.4, 5.10.267 ≤ 5.10.*, 5.15.209 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.141 ≤ 6.6.*, 6.12.91 ≤ 6.12.*, 6.18.33 ≤ 6.18.*, 7.0.10 ≤ 7.0.*, 7.1 ≤ *
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 27 May 2026 · Last source change 27 Aug 2026, 12:39 UTC · CWE-129 · Improper Validation of Array Index

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-2026-32165
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    ddc7c3042614e273044f698d2beab25cc3842d45 < a9e777f856cd2f1efc106afc7bf21aef868509d5; ddc7c3042614e273044f698d2beab25cc3842d45 < 669349b4612c26b3d7aacfa99d7174681bd19223; ddc7c3042614e273044f698d2beab25cc3842d45 < 3ff85ae79e1a74baeb916b78a63d821f6d19a994; ddc7c3042614e273044f698d2beab25cc3842d45 < 36a9012f76ba8d9189ae56a1f8bb7c87c07a1f3a; ddc7c3042614e273044f698d2beab25cc3842d45 < 76f2ebaf79a9ae6d0737b87f045fe769e425d78f; ddc7c3042614e273044f698d2beab25cc3842d45 < 99dbab7b5a12d8f58d5b0aa2f7a1fe656a70f4b2; ddc7c3042614e273044f698d2beab25cc3842d45 < 1c22483a2c4bbf747787f328392ca3e68619c4dc; 5.4 · Fixed: < 5.4; 5.15.209 ≤ 5.15.*; 6.1.175 ≤ 6.1.*; 6.6.141 ≤ 6.6.*; 6.12.91 ≤ 6.12.*; 6.18.33 ≤ 6.18.*; 7.0.10 ≤ 7.0.*; 7.1 ≤ *
    After
    ddc7c3042614e273044f698d2beab25cc3842d45 < c8e49b79c4b48bd687706ff6e9c82638dc81ef80; ddc7c3042614e273044f698d2beab25cc3842d45 < a9e777f856cd2f1efc106afc7bf21aef868509d5; ddc7c3042614e273044f698d2beab25cc3842d45 < 669349b4612c26b3d7aacfa99d7174681bd19223; ddc7c3042614e273044f698d2beab25cc3842d45 < 3ff85ae79e1a74baeb916b78a63d821f6d19a994; ddc7c3042614e273044f698d2beab25cc3842d45 < 36a9012f76ba8d9189ae56a1f8bb7c87c07a1f3a; ddc7c3042614e273044f698d2beab25cc3842d45 < 76f2ebaf79a9ae6d0737b87f045fe769e425d78f; ddc7c3042614e273044f698d2beab25cc3842d45 < 99dbab7b5a12d8f58d5b0aa2f7a1fe656a70f4b2; ddc7c3042614e273044f698d2beab25cc3842d45 < 1c22483a2c4bbf747787f328392ca3e68619c4dc · Fixed: < 5.4; 5.10.267 ≤ 5.10.*; 5.15.209 ≤ 5.15.*; 6.1.175 ≤ 6.1.*; 6.6.141 ≤ 6.6.*; 6.12.91 ≤ 6.12.*; 6.18.33 ≤ 6.18.*; 7.0.10 ≤ 7.0.*
    CNA ↗
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-2026-32165↗Vendor CSAF · SUSE Product Security Team↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗CVE authority or vendor 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-2026-45839 · cve.blacktree.nl