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.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-46116High confidence
xfrm: defensively unhash xfrm_state lists in __xfrm_state_delete
Linux · Linux
7.8HighCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productHigh technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:Medium, lowered one band.downgradedsince 15 Sep 2026
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
- Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Siemens ProductCERT: 5 affected or under-investigation product states without a fixed product state in the same current advisory
- Canonical Ubuntu Security: 20 affected package states with no published fix
Distribution package intelligence
24 package statesRelease-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.
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 release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.12.88-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.1.176-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 7.0.7-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 7.0.7-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-aws | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-azure | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-azure-fde | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-azure-nvidia | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-gcp | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-gke | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-gkeop | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-ibm | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-lowlatency | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-nvidia | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-nvidia-lowlatency | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-nvidia-tegra | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-oem-6.11 | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-oracle | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-raspi | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-raspi-realtime | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-realtime | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-riscv | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-xilinx | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Direct vendor intelligence
3 currentAuthoritative 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.
CVE-2026-46116 · CSAF 2.0 · revision 34 · interimSUSE Product Security TeamCVE-2026-46116
The vendor explicitly identifies these products as affected by this CVE.
- 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
- kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- Summary
- In the Linux kernel, the following vulnerability has been resolved: xfrm: defensively unhash xfrm_state lists in __xfrm_state_delete KASAN reproduces a slab-use-after-free in __xfrm_state_delete()'s hlist_del_rcu calls under syzkaller load on linux-6.12.y stable (reproduced on 6.12.47, also reachable via the same code path on torvalds/master and on the ipsec tree). Nine unique signatures cluster in the xfrm_state lifecycle, the load-bearing one being: BUG: KASAN: slab-use-after-free in __hlist_del include/linux/list.h:990 [inline] BUG: KASAN: slab-use-after-free in hlist_del_rcu include/linux/rculist.h:516 [inline] BUG: KASAN: slab-use-after-free in __xfrm_state_delete net/xfrm/xfrm_state.c Write of size 8 at addr ffff8881198bcb70 by task kworker/u8:9/435 Workqueue: netns cleanup_net Call Trace: __hlist_del / hlist_del_rcu __xfrm_state_delete xfrm_state_delete xfrm_state_flush xfrm_state_fini ops_exit_list cleanup_net The other observed signatures hit the same slab object from __xfrm_state_lookup, xfrm_alloc_spi, __xfrm_state_insert and an OOB write variant of __xfrm_state_delete, all on the byseq/byspi hash chains. __xfrm_state_delete() guards its byseq and byspi unhashes with value-based predicates: if (x->km.seq) hlist_del_rcu(&x->byseq); if (x->id.spi) hlist_del_rcu(&x->byspi); while everywhere else in the file (e.g. state_cache, state_cache_input) the safer hlist_unhashed() check is used. xfrm_alloc_spi() sets x->id.spi = newspi inside xfrm_state_lock and then immediately inserts into byspi, but a path that observes x->id.spi != 0 outside of xfrm_state_lock can still skip-or-hit the byspi unhash inconsistently with whether x is actually on the list. The same holds for x->km.seq versus byseq, and the bydst/bysrc unhashes have no predicate at all, so a second __xfrm_state_delete() on the same object writes through LIST_POISON pprev. The defensive change here: - Use hlist_del_init_rcu() instead of hlist_del_rcu() on bydst, bysrc, byseq and byspi so a second deletion is a no-op rather than a write through LIST_POISON pprev. The byseq/byspi nodes are already initialised in xfrm_state_alloc(). - Test hlist_unhashed() rather than the value predicate for byseq/byspi, so the unhash decision tracks list state rather than mutable scalar fields. Empirical verification: applied this patch on top of v6.12.47, rebuilt, and re-ran the same syzkaller harness for 1h16m on a previously-crashy configuration that produced ~100 hits each of slab-use-after-free Read in xfrm_alloc_spi / Read in __xfrm_state_lookup / Write in __xfrm_state_delete. After the patch, 7.1M execs across 32 VMs at ~1550 exec/sec produced zero xfrm_state UAF/OOB hits. /proc/slabinfo confirms the xfrm_state slab is actively allocated and freed during the run (~143 KiB resident), so the fuzzer is still exercising those code paths -- they just no longer crash. Reproduction: - Linux 6.12.47 x86_64 + KASAN_GENERIC + KASAN_INLINE + KCOV - syzkaller @ 746545b8b1e4c3a128db8652b340d3df90ce61db - 32 QEMU/KVM VMs x 2 vCPU on AWS c5.metal bare metal - 9 unique signatures collected in ~9h, all within xfrm_state lifecycle
- Remediation
- To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-46116 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: xfrm: defensively unhash xfrm_state lists in __xfrm_state_delete
The vendor explicitly identifies these products as affected by this CVE.
- kernel-rt as a component of Red Hat Enterprise Linux 9
- kernel-rt-core as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9
- Summary
- A flaw was found in the Linux kernel's `xfrm` (IPSec framework) subsystem. This vulnerability, a use-after-free, occurs when the system incorrectly manages memory related to security policies, specifically during the deletion of `xfrm_state` lists. An attacker with local access could exploit this flaw by triggering specific operations, leading to memory corruption. This could cause the system to become unstable, resulting in crashes or a Denial of Service (DoS), and potentially allow for unauthorized access to sensitive information or increased privileges.
- Remediation
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
The vendor explicitly identifies these products as affected by this CVE.
- SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
- SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
- SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
- SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
- SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
- Summary
- In the Linux kernel, the following vulnerability has been resolved: xfrm: defensively unhash xfrm_state lists in __xfrm_state_delete KASAN reproduces a slab-use-after-free in __xfrm_state_delete()'s hlist_del_rcu calls under syzkaller load on linux-6.12.y stable (reproduced on 6.12.47, also reachable via the same code path on torvalds/master and on the ipsec tree). Nine unique signatures cluster in the xfrm_state lifecycle, the load-bearing one being: BUG: KASAN: slab-use-after-free in __hlist_del include/linux/list.h:990 [inline] BUG: KASAN: slab-use-after-free in hlist_del_rcu include/linux/rculist.h:516 [inline] BUG: KASAN: slab-use-after-free in __xfrm_state_delete net/xfrm/xfrm_state.c Write of size 8 at addr ffff8881198bcb70 by task kworker/u8:9/435 Workqueue: netns cleanup_net Call Trace: __hlist_del / hlist_del_rcu __xfrm_state_delete xfrm_state_delete xfrm_state_flush xfrm_state_fini ops_exit_list cleanup_net The other observed signatures hit the same slab object from __xfrm_state_lookup, xfrm_alloc_spi, __xfrm_state_insert and an OOB write variant of __xfrm_state_delete, all on the byseq/byspi hash chains. __xfrm_state_delete() guards its byseq and byspi unhashes with value-based predicates: if (x->km.seq) hlist_del_rcu(&x->byseq); if (x->id.spi) hlist_del_rcu(&x->byspi); while everywhere else in the file (e.g. state_cache, state_cache_input) the safer hlist_unhashed() check is used. xfrm_alloc_spi() sets x->id.spi = newspi inside xfrm_state_lock and then immediately inserts into byspi, but a path that observes x->id.spi != 0 outside of xfrm_state_lock can still skip-or-hit the byspi unhash inconsistently with whether x is actually on the list. The same holds for x->km.seq versus byseq, and the bydst/bysrc unhashes have no predicate at all, so a second __xfrm_state_delete() on the same object writes through LIST_POISON pprev. The defensive change here: - Use hlist_del_init_rcu() instead of hlist_del_rcu() on bydst, bysrc, byseq and byspi so a second deletion is a no-op rather than a write through LIST_POISON pprev. The byseq/byspi nodes are already initialised in xfrm_state_alloc(). - Test hlist_unhashed() rather than the value predicate for byseq/byspi, so the unhash decision tracks list state rather than mutable scalar fields. Empirical verification: applied this patch on top of v6.12.47, rebuilt, and re-ran the same syzkaller harness for 1h16m on a previously-crashy configuration that produced ~100 hits each of slab-use-after-free Read in xfrm_alloc_spi / Read in __xfrm_state_lookup / Write in __xfrm_state_delete. After the patch, 7.1M execs across 32 VMs at ~1550 exec/sec produced zero xfrm_state UAF/OOB hits. /proc/slabinfo confirms the xfrm_state slab is actively allocated and freed during the run (~143 KiB resident), so the fuzzer is still exercising those code paths -- they just no longer crash. Reproduction: - Linux 6.12.47 x86_64 + KASAN_GENERIC + KASAN_INLINE + KCOV - syzkaller @ 746545b8b1e4c3a128db8652b340d3df90ce61db - 32 QEMU/KVM VMs x 2 vCPU on AWS c5.metal bare metal - 9 unique signatures collected in ~9h, all within xfrm_state lifecycle
- Remediation
- Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
In the Linux kernel, the following vulnerability has been resolved: xfrm: defensively unhash xfrm_state lists in __xfrm_state_delete KASAN reproduces a slab-use-after-free in __xfrm_state_delete()'s hlist_del_rcu calls under syzkaller load on linux-6.12.y stable (reproduced on 6.12.47, also reachable via the same code path on torvalds/master and on the ipsec tree). Nine unique signatures cluster in the xfrm_state lifecycle, the load-bearing one being: BUG: KASAN: slab-use-after-free in __hlist_del include/linux/list.h:990 [inline] BUG: KASAN: slab-use-after-free in hlist_del_rcu include/linux/rculist.h:516 [inline] BUG: KASAN: slab-use-after-free in __xfrm_state_delete net/xfrm/xfrm_state.c Write of size 8 at addr ffff8881198bcb70 by task kworker/u8:9/435 Workqueue: netns cleanup_net Call Trace: __hlist_del / hlist_del_rcu __xfrm_state_delete xfrm_state_delete xfrm_state_flush xfrm_state_fini ops_exit_list cleanup_net The other observed signatures hit the same slab object from __xfrm_state_lookup, xfrm_alloc_spi, __xfrm_state_insert and an OOB write variant of __xfrm_state_delete, all on the byseq/byspi hash chains. __xfrm_state_delete() guards its byseq and byspi unhashes with value-based predicates: if (x->km.seq) hlist_del_rcu(&x->byseq); if (x->id.spi) hlist_del_rcu(&x->byspi); while everywhere else in the file (e.g. state_cache, state_cache_input) the safer hlist_unhashed() check is used. xfrm_alloc_spi() sets x->id.spi = newspi inside xfrm_state_lock and then immediately inserts into byspi, but a path that observes x->id.spi != 0 outside of xfrm_state_lock can still skip-or-hit the byspi unhash inconsistently with whether x is actually on the list. The same holds for x->km.seq versus byseq, and the bydst/bysrc unhashes have no predicate at all, so a second __xfrm_state_delete() on the same object writes through LIST_POISON pprev. The defensive change here: - Use hlist_del_init_rcu() instead of hlist_del_rcu() on bydst, bysrc, byseq and byspi so a second deletion is a no-op rather than a write through LIST_POISON pprev. The byseq/byspi nodes are already initialised in xfrm_state_alloc(). - Test hlist_unhashed() rather than the value predicate for byseq/byspi, so the unhash decision tracks list state rather than mutable scalar fields. Empirical verification: applied this patch on top of v6.12.47, rebuilt, and re-ran the same syzkaller harness for 1h16m on a previously-crashy configuration that produced ~100 hits each of slab-use-after-free Read in xfrm_alloc_spi / Read in __xfrm_state_lookup / Write in __xfrm_state_delete. After the patch, 7.1M execs across 32 VMs at ~1550 exec/sec produced zero xfrm_state UAF/OOB hits. /proc/slabinfo confirms the xfrm_state slab is actively allocated and freed during the run (~143 KiB resident), so the fuzzer is still exercising those code paths -- they just no longer crash. Reproduction: - Linux 6.12.47 x86_64 + KASAN_GENERIC + KASAN_INLINE + KCOV - syzkaller @ 746545b8b1e4c3a128db8652b340d3df90ce61db - 32 QEMU/KVM VMs x 2 vCPU on AWS c5.metal bare metal - 9 unique signatures collected in ~9h, all within xfrm_state lifecycle
What
In the Linux kernel, the following vulnerability has been resolved: xfrm: defensively unhash xfrm_state lists in __xfrm_state_delete KASAN reproduces a slab-use-after-free in __xfrm_state_delete()'s hlist_del_rcu calls under syzkaller load on linux-6.12.y stable (reproduced on 6.12.47, also reachable via the same code path on torvalds/master and on the ipsec tree). Nine unique signatures cluster in the xfrm_state lifecycle, the load-bearing one being: BUG: KASAN: slab-use-after-free in __hlist_del include/linux/list.h:990 [inline] BUG: KASAN: slab-use-after-free in hlist_del_rcu include/linux/rculist.h:516 [inline] BUG: KASAN: slab-use-after-free in __xfrm_state_delete net/xfrm/xfrm_state.c Write of size 8 at addr ffff8881198bcb70 by task kworker/u8:9/435 Workqueue: netns cleanup_net Call Trace: __hlist_del / hlist_del_rcu __xfrm_state_delete xfrm_state_delete xfrm_state_flush xfrm_state_fini ops_exit_list cleanup_net The other observed signatures hit the same slab object from __xfrm_state_lookup, xfrm_alloc_spi, __xfrm_state_insert and an OOB write variant of __xfrm_state_delete, all on the byseq/byspi hash chains. __xfrm_state_delete() guards its byseq and byspi unhashes with value-based predicates: if (x->km.seq) hlist_del_rcu(&x->byseq); if (x->id.spi) hlist_del_rcu(&x->byspi); while everywhere else in the file (e.g. state_cache, state_cache_input) the safer hlist_unhashed() check is used. xfrm_alloc_spi() sets x->id.spi = newspi inside xfrm_state_lock and then immediately inserts into byspi, but a path that observes x->id.spi != 0 outside of xfrm_state_lock can still skip-or-hit the byspi unhash inconsistently with whether x is actually on the list. The same holds for x->km.seq versus byseq, and the bydst/bysrc unhashes have no predicate at all, so a second __xfrm_state_delete() on the same object writes through LIST_POISON pprev. The defensive change here: - Use hlist_del_init_rcu() instead of hlist_del_rcu() on bydst, bysrc, byseq and byspi so a second deletion is a no-op rather than a write through LIST_POISON pprev. The byseq/byspi nodes are already initialised in xfrm_state_alloc(). - Test hlist_unhashed() rather than the value predicate for byseq/byspi, so the unhash decision tracks list state rather than mutable scalar fields. Empirical verification: applied this patch on top of v6.12.47, rebuilt, and re-ran the same syzkaller harness for 1h16m on a previously-crashy configuration that produced ~100 hits each of slab-use-after-free Read in xfrm_alloc_spi / Read in __xfrm_state_lookup / Write in __xfrm_state_delete. After the patch, 7.1M execs across 32 VMs at ~1550 exec/sec produced zero xfrm_state UAF/OOB hits. /proc/slabinfo confirms the xfrm_state slab is actively allocated and freed during the run (~143 KiB resident), so the fuzzer is still exercising those code paths -- they just no longer crash. Reproduction: - Linux 6.12.47 x86_64 + KASAN_GENERIC + KASAN_INLINE + KCOV - syzkaller @ 746545b8b1e4c3a128db8652b340d3df90ce61db - 32 QEMU/KVM VMs x 2 vCPU on AWS c5.metal bare metal - 9 unique signatures collected in ~9h, all within xfrm_state lifecycle
Why
The product attempts to return a memory resource to the system, but it calls the wrong release function or calls the appropriate release function incorrectly.
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: xfrm: defensively unhash xfrm_state lists in __xfrm_state_delete KASAN reproduces a slab-use-after-free in __xfrm_state_delete()'s hlist_del_rcu calls under syzkaller load on linux-6.12.y stable (reproduced on 6.12.47, also reachable via the same code path on torvalds/master and on the ipsec tree). Nine unique signatures cluster in the xfrm_state lifecycle, the load-bearing one being: BUG: KASAN: slab-use-after-free in __hlist_del include/linux/list.h:990 [inline] BUG: KASAN: slab-use-after-free in hlist_del_rcu include/linux/rculist.h:516 [inline] BUG: KASAN: slab-use-after-free in __xfrm_state_delete net/xfrm/xfrm_state.c Write of size 8 at addr ffff8881198bcb70 by task kworker/u8:9/435 Workqueue: netns cleanup_net Call Trace: __hlist_del / hlist_del_rcu __xfrm_state_delete xfrm_state_delete xfrm_state_flush xfrm_state_fini ops_exit_list cleanup_net The other observed signatures hit the same slab object from __xfrm_state_lookup, xfrm_alloc_spi, __xfrm_state_insert and an OOB write variant of __xfrm_state_delete, all on the byseq/byspi hash chains. __xfrm_state_delete() guards its byseq and byspi unhashes with value-based predicates: if (x->km.seq) hlist_del_rcu(&x->byseq); if (x->id.spi) hlist_del_rcu(&x->byspi); while everywhere else in the file (e.g. state_cache, state_cache_input) the safer hlist_unhashed() check is used. xfrm_alloc_spi() sets x->id.spi = newspi inside xfrm_state_lock and then immediately inserts into byspi, but a path that observes x->id.spi != 0 outside of xfrm_state_lock can still skip-or-hit the byspi unhash inconsistently with whether x is actually on the list. The same holds for x->km.seq versus byseq, and the bydst/bysrc unhashes have no predicate at all, so a second __xfrm_state_delete() on the same object writes through LIST_POISON pprev. The defensive change here: - Use hlist_del_init_rcu() instead of hlist_del_rcu() on bydst, bysrc, byseq and byspi so a second deletion is a no-op rather than a write through LIST_POISON pprev. The byseq/byspi nodes are already initialised in xfrm_state_alloc(). - Test hlist_unhashed() rather than the value predicate for byseq/byspi, so the unhash decision tracks list state rather than mutable scalar fields. Empirical verification: applied this patch on top of v6.12.47, rebuilt, and re-ran the same syzkaller harness for 1h16m on a previously-crashy configuration that produced ~100 hits each of slab-use-after-free Read in xfrm_alloc_spi / Read in __xfrm_state_lookup / Write in __xfrm_state_delete. After the patch, 7.1M execs across 32 VMs at ~1550 exec/sec produced zero xfrm_state UAF/OOB hits. /proc/slabinfo confirms the xfrm_state slab is actively allocated and freed during the run (~143 KiB resident), so the fuzzer is still exercising those code paths -- they just no longer crash. Reproduction: - Linux 6.12.47 x86_64 + KASAN_GENERIC + KASAN_INLINE + KCOV - syzkaller @ 746545b8b1e4c3a128db8652b340d3df90ce61db - 32 QEMU/KVM VMs x 2 vCPU on AWS c5.metal bare metal - 9 unique signatures collected in ~9h, all within xfrm_state lifecycle
Why
The product attempts to return a memory resource to the system, but it calls the wrong release function or calls the appropriate release function incorrectly.
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 No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.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 None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.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 → Release of Invalid Pointer or Reference → 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-763 ↗
CWE-763: Release of Invalid Pointer or Reference. The product attempts to return a memory resource to the system, but it calls the wrong release function or calls the appropriate release function incorrectly.
- 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:HCommon 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.
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
- 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
- kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- 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
- SUSE Linux Enterprise Live Patching 12 SP5:kgraft-patch-4_12_14-122_283-default
- SUSE Linux Enterprise Live Patching 12 SP5:kgraft-patch-4_12_14-122_293-default
- SUSE Linux Enterprise Live Patching 12 SP5:kgraft-patch-4_12_14-122_296-default
- and 134 more
- 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 28 May 2026 · Last source change 15 Sept 2026, 12:04 UTC · CWE-763 · Release of Invalid Pointer or Reference
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-32875
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceOther authority
NVD statusNVD enrichment underway
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.SUSE Product Security Team ↗
- Before
- 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; kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4; kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1; reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1; 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; SUSE Linux Enterprise Live Patching 12 SP5:kgraft-patch-4_12_14-122_283-default; SUSE Linux Enterprise Live Patching 12 SP5:kgraft-patch-4_12_14-122_293-default; SUSE Linux Enterprise Live Patching 12 SP5:kgraft-patch-4_12_14-122_296-default; and 175 more
- After
- 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; kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4; kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1; reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1; 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; SUSE Linux Enterprise Live Patching 12 SP5:kgraft-patch-4_12_14-122_283-default; SUSE Linux Enterprise Live Patching 12 SP5:kgraft-patch-4_12_14-122_293-default; SUSE Linux Enterprise Live Patching 12 SP5:kgraft-patch-4_12_14-122_296-default; and 134 more
- Affected versionsThe structured affected or fixed version information changed.SUSE Product Security Team ↗
- Before
- 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; kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4; kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1; reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1; 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; SUSE Linux Enterprise Live Patching 12 SP5:kgraft-patch-4_12_14-122_275-default; SUSE Linux Enterprise Live Patching 12 SP5:kgraft-patch-4_12_14-122_280-default; SUSE Linux Enterprise Live Patching 12 SP5:kgraft-patch-4_12_14-122_283-default; and 178 more
- After
- 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; kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4; kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1; reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1; 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; SUSE Linux Enterprise Live Patching 12 SP5:kgraft-patch-4_12_14-122_283-default; SUSE Linux Enterprise Live Patching 12 SP5:kgraft-patch-4_12_14-122_293-default; SUSE Linux Enterprise Live Patching 12 SP5:kgraft-patch-4_12_14-122_296-default; and 175 more
- Affected versionsThe structured affected or fixed version information changed.SUSE Product Security Team ↗
- Before
- 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; kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4; kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1; reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1; 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; kernel-default as component of SUSE Linux Enterprise Micro 5.0; kernel-default as component of SUSE Linux Enterprise Micro 5.1; kernel-default as component of SUSE Linux Enterprise Micro 5.2; and 100 more
- After
- 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; kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4; kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1; reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1; 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; SUSE Linux Enterprise Live Patching 12 SP5:kgraft-patch-4_12_14-122_275-default; SUSE Linux Enterprise Live Patching 12 SP5:kgraft-patch-4_12_14-122_280-default; SUSE Linux Enterprise Live Patching 12 SP5:kgraft-patch-4_12_14-122_283-default; and 178 more
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 7b4dc3600e4877178ba94c7fbf7e520421378aa6 < 6b4dc3181b4bfc5f5fc33ab33b1dc6e15759f4b6; 7b4dc3600e4877178ba94c7fbf7e520421378aa6 < 3943fcad7694a7d0b15aeabe7d3cc2a2eb8e92e8; 7b4dc3600e4877178ba94c7fbf7e520421378aa6 < 2c617848ae6e4f07a3e397f604208c293bbecacc; 7b4dc3600e4877178ba94c7fbf7e520421378aa6 < b4a53add2fa8f1b5aa17d4c5686c320785fab182; 7b4dc3600e4877178ba94c7fbf7e520421378aa6 < 26edb0a3c99f9d958c212be68b21f1221614dcf0; 7b4dc3600e4877178ba94c7fbf7e520421378aa6 < 4980162de555cb838f1a189ce7d2cbf5d2e7b050; 7b4dc3600e4877178ba94c7fbf7e520421378aa6 < a2e2d08fb070fab4947447171f1c4e3ca5a188e5; 7b4dc3600e4877178ba94c7fbf7e520421378aa6 < 14acf9652e5690de3c7486c6db5fb8dafd0a32a3 · Fixed: < 2.6.19; 5.10.261 ≤ 5.10.*; 5.15.210 ≤ 5.15.*; 6.1.176 ≤ 6.1.*; 6.6.140 ≤ 6.6.*; 6.12.88 ≤ 6.12.*; 6.18.30 ≤ 6.18.*; 7.0.7 ≤ 7.0.*
- After
- Linux: 7b4dc3600e4877178ba94c7fbf7e520421378aa6 < 6b4dc3181b4bfc5f5fc33ab33b1dc6e15759f4b6, 7b4dc3600e4877178ba94c7fbf7e520421378aa6 < 3943fcad7694a7d0b15aeabe7d3cc2a2eb8e92e8, 7b4dc3600e4877178ba94c7fbf7e520421378aa6 < 2c617848ae6e4f07a3e397f604208c293bbecacc, 7b4dc3600e4877178ba94c7fbf7e520421378aa6 < b4a53add2fa8f1b5aa17d4c5686c320785fab182, 7b4dc3600e4877178ba94c7fbf7e520421378aa6 < 26edb0a3c99f9d958c212be68b21f1221614dcf0, 7b4dc3600e4877178ba94c7fbf7e520421378aa6 < 4980162de555cb838f1a189ce7d2cbf5d2e7b050, 7b4dc3600e4877178ba94c7fbf7e520421378aa6 < a2e2d08fb070fab4947447171f1c4e3ca5a188e5, 7b4dc3600e4877178ba94c7fbf7e520421378aa6 < 14acf9652e5690de3c7486c6db5fb8dafd0a32a3, 2.6.19 · Fixed: Linux: < 2.6.19, 5.10.261 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.176 ≤ 6.1.*, 6.6.140 ≤ 6.6.*, 6.12.88 ≤ 6.12.*, 6.18.30 ≤ 6.18.*, 7.0.7 ≤ 7.0.*, 7.1 ≤ *
- Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:59142; removed vendor advisory: access.redhat.com/RHSA-2026:59143; 5 further removals.git.kernel.org ↗
- Before
- patch: git.kernel.org/14acf9652e5690de3c7486c6db5fb8dafd0a32a3 · patch: git.kernel.org/26edb0a3c99f9d958c212be68b21f1221614dcf0 · patch: git.kernel.org/2c617848ae6e4f07a3e397f604208c293bbecacc · 12 more references
- After
- patch: git.kernel.org/14acf9652e5690de3c7486c6db5fb8dafd0a32a3 · patch: git.kernel.org/26edb0a3c99f9d958c212be68b21f1221614dcf0 · patch: git.kernel.org/2c617848ae6e4f07a3e397f604208c293bbecacc · 5 more references
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:59142; added vendor advisory: access.redhat.com/RHSA-2026:59143; 5 further additions.git.kernel.org ↗
- Before
- patch: git.kernel.org/14acf9652e5690de3c7486c6db5fb8dafd0a32a3 · patch: git.kernel.org/26edb0a3c99f9d958c212be68b21f1221614dcf0 · patch: git.kernel.org/2c617848ae6e4f07a3e397f604208c293bbecacc · 5 more references
- After
- patch: git.kernel.org/14acf9652e5690de3c7486c6db5fb8dafd0a32a3 · patch: git.kernel.org/26edb0a3c99f9d958c212be68b21f1221614dcf0 · patch: git.kernel.org/2c617848ae6e4f07a3e397f604208c293bbecacc · 12 more references
CVE published
Fixed release or patch reference recorded
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.