HighCVE-2026-98959

    Linux Kernel: Mehrere Schwachstellen

    Published Sources: BSI

    What is affected, what to do

    In the Linux kernel, the following vulnerability has been resolved: btrfs: fix xattr replace when multiple xattrs are packed in the same item If we have a btrfs_dir_item item that packs multiple xattrs and then we replace the value of one of them (with the setxattr(2) family of syscalls) with another value of a different size, we end up not having a fully initialized btrfs_dir_item, resulting in a corruption that the tree checker will detect at extent buffer writeback time. This is because in btrfs_setxattr() when we find a btrfs_dir_item with multiple xattrs (due to the crc32c hash of their name being the same) we delete one of the xattr items (btrfs_dir_item) and then insert a new one, but the deletion and insertion results in shifting existing data in the leaf and therefore when the new value of a xattr has a different size, the new btrfs_dir_item is placed in a leaf section that was not initialized and we only copy the value's data and set the value's length in the new btrfs_dir_item, without setting the name, the name's length, the key (which must be all zeroes for xattrs), flags (BTRFS_FT_XATTR) and transaction ID.

    The available sources name no fixed version. Check the vendor guidance in the references below.

    Conflicting version data — version display is hidden until the data is resolved.

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.1

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    7.1

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: BSI

    0.6 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 48.9

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    57.81 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.1 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.1
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.6 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    48.9
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    In the Linux kernel, the following vulnerability has been resolved: btrfs: fix xattr replace when multiple xattrs are packed in the same item If we have a btrfs_dir_item item that packs multiple xattrs and then we replace the value of one of them (with the setxattr(2) family of syscalls) with another value of a different size, we end up not having a fully initialized btrfs_dir_item, resulting in a corruption that the tree checker will detect at extent buffer writeback time. This is because in btrfs_setxattr() when we find a btrfs_dir_item with multiple xattrs (due to the crc32c hash of their name being the same) we delete one of the xattr items (btrfs_dir_item) and then insert a new one, but the deletion and insertion results in shifting existing data in the leaf and therefore when the new value of a xattr has a different size, the new btrfs_dir_item is placed in a leaf section that was not initialized and we only copy the value's data and set the value's length in the new btrfs_dir_item, without setting the name, the name's length, the key (which must be all zeroes for xattrs), flags (BTRFS_FT_XATTR) and transaction ID. The following script reproduces the issue: $ cat test.sh #!/bin/bash DEV=/dev/sdi MNT=/mnt/sdi mkfs.btrfs -f $DEV mount $DEV $MNT touch $MNT/testfile # Add two xattrs that, on btrfs, have the same hash (crc32c) for their # name and therefore are packed into the same btrfs_dir_item. setfattr -n user.foobar -v 123 $MNT/testfile setfattr -n user.WvG1c1Td -v qwerty $MNT/testfile # Verify the xattrs are present. echo "xattrs before:" getfattr --absolute-names --dump $MNT/testfile # Now replace the value of the foobar xattr with a significantly larger # value. setfattr -n user.foobar -v abcdefghijklmnopqrstuvwxyz $MNT/testfile # Check the xattrs have the expected values. echo "xattrs after:" getfattr --absolute-names --dump $MNT/testfile umount $MNT Running it: $ ./test.sh (...) xattrs before: # file: /mnt/sdi/testfile user.WvG1c1Td="qwerty" user.foobar="123" xattrs after: # file: /mnt/sdi/testfile user.WvG1c1Td="qwerty" So the "user.foobar" xattr is missing and there was a transaction abort when unmounting the fs with the following traces in dmesg: $ dmesg [869800.159271] BTRFS warning (device sdi): access to eb bytenr 30474240 len 16384 out of range start 16015 len 25964 [869800.159293] ------------[ cut here ]------------ [869800.159296] WARNING: fs/btrfs/extent_io.c:4408 at report_eb_range+0x44/0x60 [btrfs], CPU#8: getfattr/2605179 [869800.168961] Modules linked in: btrfs dm_thin_pool (...) [869800.190527] CPU: 8 UID: 0 PID: 2605179 Comm: getfattr Tainted: G W 7.3.0-rc3-btrfs-next-244+ #1 PREEMPT(full) [869800.193726] Tainted: [W]=WARN [869800.194502] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-0-gea1b7a073390-prebuilt.qemu.org 04/01/2014 [869800.197576] RIP: 0010:report_eb_range+0x44/0x60 [btrfs] [869800.198985] Code: 48 8b 7b 18 (...) [869800.203531] RSP: 0018:ffffce4541937d58 EFLAGS: 00010246 [869800.204609] RAX: 0000000000000000 RBX: ffff8dde054b8738 RCX: 0000000000000000 [869800.206137] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffffffc04c92a0 [869800.207645] RBP: 0000000000003e8f R08: 0000000000000000 R09: 3fffffffffefffff [869800.226175] R10: ffffce4541937a88 R11: 0000000000000003 R12: 000000000000656c [869800.227594] R13: ffff8dde14be800f R14: 000000000000656c R15: 0000000000000069 [869800.229097] FS: 00007f59023bb780(0000) GS:ffff8de5788ed000(0000) knlGS:0000000000000000 [869800.231137] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [869800.232321] CR2: 0000558dc45e6a78 CR3: 0000000765b16004 CR4: 0000000000370ef0 [869800.233783] Call Trace: [869800.234330] <TASK> [869800.234791] read_extent_buffer+0x4d/0x100 [btrfs] [869800.235898] btrfs_listxattr+0x199/0x240 [btrfs] [869800.236912] vfs_listxattr+0x51/0 ---truncated---

    Source: BSI WID Portal

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    LinuxLinux
    • 2.6.12 – < 5.10.271
    • 2.6.12 – < 6.6.160
    • 2.6.13 – < 6.6.160
    • 2.6.22 – < 5.10.271
    • 2.6.24 – < 5.15.222
    • 2.6.25 – < 6.6.160
    • 2.6.29 – < 6.6.160
    • 2.6.31 – < 6.12.113
    • 2.6.39 – < 5.10.271
    • 3.1 – < 5.10.271
    • 3.10.83 – < 3.11
    • 3.11 – < 6.6.160
    • 3.12 – < 6.18.57
    • 3.12 – < 6.6.160
    • 3.12.45 – < 3.13
    • 3.14.47 – < 3.15
    • 3.16 – < 6.6.160
    • 3.17 – < 5.10.271
    • 3.18 – < 6.12.113
    • 3.18 – < 6.6.160
    • 3.18.19 – < 3.19
    • 3.19 – < 6.18.57
    • 3.19 – < 6.6.160
    • 3.2 – < 6.6.160
    • 3.4 – < 5.10.271
    • 3.6 – < 6.18.57
    • 3.6 – < 6.18.59
    • 3.7 – < 5.10.271
    • 3.7 – < 6.6.160
    • 3.8.6 – < 3.9
    • 3.9 – < 6.12.113
    • 3.9 – < 6.6.160
    • 4.0 – < 6.12.112
    • 4.0.2 – < 4.1
    • 4.1 – < 5.10.271
    • 4.1 – < 6.6.160
    • 4.10.3 – < 4.11
    • 4.11 – < 6.6.160
    • 4.11.12 – < 4.12
    • 4.12 – < 6.6.160
    • 4.12.3 – < 4.13
    • 4.13 – < 6.18.57
    • 4.13 – < 6.6.160
    • 4.14 – < 6.6.160
    • 4.14 – < 7.2.11
    • 4.1.40 – < 4.2
    • 4.14.16 – < 4.15
    • 4.14.226 – < 4.15
    • 5.10.271
    • 6.6.160
    • 6.6.160
    • 5.10.271
    • 5.15.222
    • 6.6.160
    • 6.6.160
    • 6.12.113
    • 5.10.271
    • 5.10.271
    • 3.11
    • 6.6.160
    • 6.18.57
    • 6.6.160
    • 3.13
    • 3.15
    • 6.6.160
    • 5.10.271
    • 6.12.113
    • 6.6.160
    • 3.19
    • 6.18.57
    • 6.6.160
    • 6.6.160
    • 5.10.271
    • 6.18.57
    • 6.18.59
    • 5.10.271
    • 6.6.160
    • 3.9
    • 6.12.113
    • 6.6.160
    • 6.12.112
    • 4.1
    • 5.10.271
    • 6.6.160
    • 4.11
    • 6.6.160
    • 4.12
    • 6.6.160
    • 4.13
    • 6.18.57
    • 6.6.160
    • 6.6.160
    • 7.2.11
    • 4.2
    • 4.15
    • 4.15
    From bundled advisories, not CVE-specific (8)

    Product list of a bundled advisory that does not state which product this CVE affects.

    Products from bundled advisories
    Affected versionsFixed in
    DellPowerProtect Data Domain
    • < 7.10.1.70
    • < 7.13.1.40
    • < 8.3.1.10
    • < 8.4.0.0
    • 7.10.1.70
    • 7.13.1.40
    • 8.3.1.10
    • 8.4.0.0
    DellPowerScale OneFS
    • < 4.0.33
    • 4.0.33
    IBMDataPower Gateway
    • < 10.6.6.0
    • 10.6.6.0
    IBMQRadar SIEM
    • <7.5.0 UP11 IF02
    • —
    SiemensSIMATIC S7
    • 1500 CPU
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxlinuxlinux_kernel6.12
    Linuxlinuxlinux_kernel—

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedLinux

      CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      CVSSadded
      —
      AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

      Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    2. ReceivedLinux

      Description added or changed

      Show 7 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      In the Linux kernel, the following vulnerability has been resolved: btrfs: fix xattr replace when multiple xattrs are packed in the same item If we have a btrfs_dir_item item that packs multiple xattrs and then we replace the value of one of them (with the setxattr(2) family of syscalls) with another value of a different size, we end up not having a fully initialized btrfs_dir_item, resulting in a corruption that the tree checker will detect at extent buffer writeback time. This is because in btrfs_setxattr() when we find a btrfs_dir_item with multiple xattrs (due to the crc32c hash of their name being the same) we delete one of the xattr items (btrfs_dir_item) and then insert a new one, but the deletion and insertion results in shifting existing data in the leaf and therefore when the new value of a xattr has a different size, the new btrfs_dir_item is placed in a leaf section that was not initialized and we only copy the value's data and set the value's length in the new btrfs_dir_item, without setting the name, the name's length, the key (which must be all zeroes for xattrs), flags (BTRFS_FT_XATTR) and transaction ID. The following script reproduces the issue: $ cat test.sh #!/bin/bash DEV=/dev/sdi MNT=/mnt/sdi mkfs.btrfs -f $DEV mount $DEV $MNT touch $MNT/testfile # Add two xattrs that, on btrfs, have the same hash (crc32c) for their # name and therefore are packed into the same btrfs_dir_item. setfattr -n user.foobar -v 123 $MNT/testfile setfattr -n user.WvG1c1Td -v qwerty $MNT/testfile # Verify the xattrs are present. echo "xattrs before:" getfattr --absolute-names --dump $MNT/testfile # Now replace the value of the foobar xattr with a significantly larger # value. setfattr -n user.foobar -v abcdefghijklmnopqrstuvwxyz $MNT/testfile # Check the xattrs have the expected values. echo "xattrs after:" getfattr --absolute-names --dump $MNT/testfile umount $MNT Running it: $ ./test.sh (...) xattrs before: # file: /mnt/sdi/testfile user.WvG1c1Td="qwerty" user.foobar="123" xattrs after: # file: /mnt/sdi/testfile user.WvG1c1Td="qwerty" So the "user.foobar" xattr is missing and there was a transaction abort when unmounting the fs with the following traces in dmesg: $ dmesg [869800.159271] BTRFS warning (device sdi): access to eb bytenr 30474240 len 16384 out of range start 16015 len 25964 [869800.159293] ------------[ cut here ]------------ [869800.159296] WARNING: fs/btrfs/extent_io.c:4408 at report_eb_range+0x44/0x60 [btrfs], CPU#8: getfattr/2605179 [869800.168961] Modules linked in: btrfs dm_thin_pool (...) [869800.190527] CPU: 8 UID: 0 PID: 2605179 Comm: getfattr Tainted: G W 7.3.0-rc3-btrfs-next-244+ #1 PREEMPT(full) [869800.193726] Tainted: [W]=WARN [869800.194502] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-0-gea1b7a073390-prebuilt.qemu.org 04/01/2014 [869800.197576] RIP: 0010:report_eb_range+0x44/0x60 [btrfs] [869800.198985] Code: 48 8b 7b 18 (...) [869800.203531] RSP: 0018:ffffce4541937d58 EFLAGS: 00010246 [869800.204609] RAX: 0000000000000000 RBX: ffff8dde054b8738 RCX: 0000000000000000 [869800.206137] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffffffc04c92a0 [869800.207645] RBP: 0000000000003e8f R08: 0000000000000000 R09: 3fffffffffefffff [869800.226175] R10: ffffce4541937a88 R11: 0000000000000003 R12: 000000000000656c [869800.227594] R13: ffff8dde14be800f R14: 000000000000656c R15: 0000000000000069 [869800.229097] FS: 00007f59023bb780(0000) GS:ffff8de5788ed000(0000) knlGS:0000000000000000 [869800.231137] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [869800.232321] CR2: 0000558dc45e6a78 CR3: 0000000765b16004 CR4: 0000000000370ef0 [869800.233783] Call Trace: [869800.234330] <TASK> [869800.234791] read_extent_buffer+0x4d/0x100 [btrfs] [869800.235898] btrfs_listxattr+0x199/0x240 [btrfs] [869800.236912] vfs_listxattr+0x51/0 ---truncated---
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/98xxx/CVE-2026-98959.json">CVE-2026-98959</a>
      Referenceadded
      —
      https://git.kernel.org/stable/c/5877d7138cc4359d26fd7b010eedfd1b3162348f
      Referenceadded
      —
      https://git.kernel.org/stable/c/7a53bb4668b319fc6c8a3ce2c21635125c7d2712
      Referenceadded
      —
      https://git.kernel.org/stable/c/858bee1c77857aabcc2327cd32dd8266332de332
      Referenceadded
      —
      https://git.kernel.org/stable/c/a97114b9b00ed3d05156f3b2ddbf797296260389
      Referenceadded
      —
      https://git.kernel.org/stable/c/c1803697a60f22743aa28ad522f805e92d45e3f0

      Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Linked CVEs

    Linked CVEs
    MediumCVE-2026-99087Linux Kernel: NULL Pointer Dereference4.4—
    Not ratedCVE-2026-99086Linux Kernel: security vulnerability——
    Not ratedCVE-2026-99085Linux Kernel: security vulnerability——
    Not ratedCVE-2026-99084Linux Kernel: security vulnerability——
    HighCVE-2026-99083Linux Kernel: Out-of-Bounds Write8.8—
    HighCVE-2026-99082Linux Kernel: security vulnerability8.8—
    HighCVE-2026-99081Linux Kernel: security vulnerability7.5—
    MediumCVE-2026-99080Linux Kernel: security vulnerability4.7—
    CriticalCVE-2026-99079Linux Kernel: security vulnerability9.8—
    CriticalCVE-2026-99078Linux Kernel: security vulnerability9.8—
    HighCVE-2026-99077Linux Kernel: security vulnerability7.4—
    HighCVE-2026-99076Linux Kernel: security vulnerability7.4—
    Not ratedCVE-2026-99075Linux Kernel: security vulnerability——
    Not ratedCVE-2026-99074Linux Kernel: NULL Pointer Dereference——
    Not ratedCVE-2026-99073Linux Kernel: security vulnerability——
    MediumCVE-2026-99072Linux Kernel: security vulnerability4.1—
    LowCVE-2026-99071Linux Kernel: security vulnerability1.9—
    LowCVE-2026-99070Linux Kernel: security vulnerability1.9—
    Not ratedCVE-2026-99069Linux Kernel: Type Confusion——
    Not ratedCVE-2026-99068Linux Kernel: Memory Leak——
    LowCVE-2026-99067Linux Kernel: security vulnerability1.9—
    Not ratedCVE-2026-99066Linux Kernel: security vulnerability——
    Not ratedCVE-2026-99065Linux Kernel: security vulnerability——
    HighCVE-2026-99064Linux Kernel: security vulnerability8.1—
    Show 195 more CVEs
    Linked CVEs
    LowCVE-2026-99063Linux Kernel: Out-of-Bounds Read2.3—
    Not ratedCVE-2026-99062Linux Kernel: security vulnerability——
    MediumCVE-2026-99061Linux Kernel: security vulnerability4.1—
    Not ratedCVE-2026-99060Linux Kernel: Race Condition——
    HighCVE-2026-99059Linux Kernel: security vulnerability7.7—
    MediumCVE-2026-99058Linux Kernel: security vulnerability4.1—
    MediumCVE-2026-99057Linux Kernel: security vulnerability4.5—
    HighCVE-2026-99056Linux Kernel: Race Condition7.8—
    Not ratedCVE-2026-99055Linux Kernel: NULL Pointer Dereference——
    HighCVE-2026-99054Linux Kernel: Use-After-Free7.8—
    HighCVE-2026-99053Linux Kernel: Use-After-Free7.8—
    MediumCVE-2026-99052Linux Kernel: security vulnerability6.0—
    HighCVE-2026-99051Linux Kernel: Use-After-Free7.8—
    HighCVE-2026-99050Linux Kernel: Use-After-Free7.8—
    LowCVE-2026-99049Linux Kernel: security vulnerability1.9—
    Not ratedCVE-2026-99048Linux Kernel: Deadlock——
    Not ratedCVE-2026-99047Linux Kernel: security vulnerability——
    HighCVE-2026-99046Linux Kernel: security vulnerability7.5—
    MediumCVE-2026-99045Linux Kernel: security vulnerability4.7—
    Not ratedCVE-2026-99044Linux Kernel: Use-After-Free——
    MediumCVE-2026-99043Linux Kernel: security vulnerability4.7—
    HighCVE-2026-99042Linux Kernel: security vulnerability8.4—
    MediumCVE-2026-99041Linux Kernel: NULL Pointer Dereference5.5—
    MediumCVE-2026-99040Linux Kernel: security vulnerability4.7—
    MediumCVE-2026-99039Linux Kernel: Use-After-Free5.7—
    MediumCVE-2026-99038Linux Kernel: security vulnerability4.2—
    MediumCVE-2026-99037Linux Kernel: Memory Corruption6.0—
    MediumCVE-2026-99036Linux Kernel: Race Condition4.1—
    MediumCVE-2026-99035Linux Kernel: Use-After-Free4.7—
    LowCVE-2026-99034Linux Kernel: security vulnerability2.3—
    MediumCVE-2026-99033Linux Kernel: security vulnerability4.4—
    HighCVE-2026-99032Linux Kernel: Use-After-Free7.1—
    MediumCVE-2026-99031Linux Kernel: security vulnerability4.4—
    HighCVE-2026-99030Linux Kernel: security vulnerability7.5—
    Not ratedCVE-2026-99029Linux Kernel: security vulnerability——
    Not ratedCVE-2026-99028Linux Kernel: security vulnerability——
    MediumCVE-2026-99027Linux Kernel: Use-After-Free6.0—
    LowCVE-2026-99026Linux Kernel: security vulnerability2.3—
    MediumCVE-2026-99025Linux Kernel: security vulnerability4.1—
    MediumCVE-2026-99024Linux Kernel: security vulnerability5.3—
    Not ratedCVE-2026-99023Linux Kernel: Memory Leak——
    MediumCVE-2026-99022Linux Kernel: security vulnerability4.4—
    MediumCVE-2026-99021Linux Kernel: security vulnerability4.1—
    Not ratedCVE-2026-99020Linux Kernel: security vulnerability——
    LowCVE-2026-99019Linux Kernel: security vulnerability2.3—
    HighCVE-2026-99018Linux Kernel: security vulnerability7.8—
    HighCVE-2026-99017Linux Kernel: security vulnerability7.0—
    HighCVE-2026-99016Linux Kernel: security vulnerability7.8—
    MediumCVE-2026-99015Linux Kernel: Use-After-Free6.3—
    HighCVE-2026-99014Linux Kernel: Use-After-Free7.8—
    HighCVE-2026-99013Linux Kernel: Use-After-Free7.8—
    HighCVE-2026-99012Linux Kernel: Use-After-Free7.1—
    HighCVE-2026-99011Linux Kernel: Use-After-Free7.1—
    MediumCVE-2026-99010Linux Kernel: security vulnerability5.3—
    MediumCVE-2026-99009Linux Kernel: security vulnerability4.7—
    MediumCVE-2026-99008Linux Kernel: NULL Pointer Dereference4.7—
    LowCVE-2026-99007Linux Kernel: security vulnerability2.5—
    HighCVE-2026-99006Linux Kernel: security vulnerability7.1—
    LowCVE-2026-99005Linux Kernel: security vulnerability2.5—
    Not ratedCVE-2026-99004Linux Kernel: security vulnerability——
    Not ratedCVE-2026-99003Linux Kernel: security vulnerability——
    HighCVE-2026-99002Linux Kernel: Out-of-Bounds Read7.1—
    Not ratedCVE-2026-99001Linux Kernel: security vulnerability——
    Not ratedCVE-2026-99000Linux Kernel: security vulnerability——
    HighCVE-2026-98999Linux Kernel: Use-After-Free7.8—
    Not ratedCVE-2026-98998Linux Kernel: security vulnerability——
    Not ratedCVE-2026-98997Linux Kernel: security vulnerability——
    MediumCVE-2026-98996Linux Kernel: security vulnerability6.3—
    HighCVE-2026-98995Linux Kernel: security vulnerability7.8—
    Not ratedCVE-2026-98994Linux Kernel: security vulnerability——
    MediumCVE-2026-98993Linux Kernel: security vulnerability6.1—
    MediumCVE-2026-98992Linux Kernel: security vulnerability4.4—
    HighCVE-2026-98991Linux Kernel: Use-After-Free7.8—
    MediumCVE-2026-98990Linux Kernel: security vulnerability4.7—
    MediumCVE-2026-98989Linux Kernel: security vulnerability5.5—
    HighCVE-2026-98988Linux Kernel: security vulnerability8.8—
    Not ratedCVE-2026-98987Linux Kernel: security vulnerability——
    Not ratedCVE-2026-98986Linux Kernel: security vulnerability——
    MediumCVE-2026-98985Linux Kernel: Use-After-Free4.7—
    LowCVE-2026-98984Linux Kernel: security vulnerability2.5—
    Not ratedCVE-2026-98983Linux Kernel: security vulnerability——
    HighCVE-2026-98982Linux Kernel: security vulnerability7.8—
    HighCVE-2026-98981Linux Kernel: security vulnerability8.8—
    MediumCVE-2026-98980Linux Kernel: security vulnerability6.4—
    MediumCVE-2026-98979Linux Kernel: NULL Pointer Dereference5.5—
    HighCVE-2026-98978Linux Kernel: security vulnerability8.4—
    MediumCVE-2026-98977Linux Kernel: security vulnerability4.2—
    HighCVE-2026-98976Linux Kernel: security vulnerability7.8—
    MediumCVE-2026-98975Linux Kernel: security vulnerability6.1—
    HighCVE-2026-98974Linux Kernel: security vulnerability7.8—
    Not ratedCVE-2026-98973Linux Kernel: security vulnerability——
    MediumCVE-2026-98972Linux Kernel: security vulnerability4.1—
    LowCVE-2026-98971Linux Kernel: security vulnerability3.0—
    LowCVE-2026-98970Linux Kernel: security vulnerability2.3—
    LowCVE-2026-98969Linux Kernel: Out-of-Bounds Read3.3—
    HighCVE-2026-98968Linux Kernel: Use-After-Free7.7—
    MediumCVE-2026-98967Linux Kernel: security vulnerability4.1—
    LowCVE-2026-98966Linux Kernel: security vulnerability2.3—
    HighCVE-2026-98965Linux Kernel: security vulnerability7.5—
    MediumCVE-2026-98964Linux Kernel: security vulnerability5.3—
    Not ratedCVE-2026-98963Linux Kernel: security vulnerability——
    Not ratedCVE-2026-98962Linux Kernel: security vulnerability——
    Not ratedCVE-2026-98961Linux Kernel: security vulnerability——
    Not ratedCVE-2026-98960Linux Kernel: security vulnerability——
    HighCVE-2026-98959Linux Kernel: security vulnerability7.1—
    Not ratedCVE-2026-98958Linux Kernel: security vulnerability——
    MediumCVE-2026-98957Linux Kernel: security vulnerability4.4—
    LowCVE-2026-98956Linux Kernel: security vulnerability2.3—
    LowCVE-2026-98955Linux Kernel: security vulnerability3.4—
    MediumCVE-2026-98954Linux Kernel: Out-of-Bounds Access4.4—
    Not ratedCVE-2026-98953Linux Kernel: security vulnerability——
    HighCVE-2026-98952Linux Kernel: security vulnerability7.3—
    HighCVE-2026-98951Linux Kernel: security vulnerability7.1—
    LowCVE-2026-98950Linux Kernel: security vulnerability3.4—
    Not ratedCVE-2026-98949Linux Kernel: security vulnerability——
    LowCVE-2026-98948Linux Kernel: security vulnerability2.3—
    LowCVE-2026-98947Linux Kernel: Memory Leak2.6—
    MediumCVE-2026-98946Linux Kernel: NULL Pointer Dereference4.7—
    MediumCVE-2026-98945Linux Kernel: security vulnerability4.6—
    MediumCVE-2026-98944Linux Kernel: security vulnerability4.0—
    MediumCVE-2026-98943Linux Kernel: security vulnerability4.7—
    MediumCVE-2026-98942Linux Kernel: Use of Uninitialized Memory4.7—
    HighCVE-2026-98941Linux Kernel: NULL Pointer Dereference7.0—
    MediumCVE-2026-98940Linux Kernel: security vulnerability6.7—
    Not ratedCVE-2026-98939Linux Kernel: Deadlock——
    Not ratedCVE-2026-98938Linux Kernel: Use of Uninitialized Memory——
    LowCVE-2026-98937Linux Kernel: security vulnerability3.3—
    LowCVE-2026-98936Linux Kernel: security vulnerability1.9—
    LowCVE-2026-98935Linux Kernel: Information Disclosure3.3—
    LowCVE-2026-98934Linux Kernel: security vulnerability1.9—
    Not ratedCVE-2026-98933Linux Kernel: security vulnerability——
    MediumCVE-2026-98932Linux Kernel: Use-After-Free5.1—
    MediumCVE-2026-98931Linux Kernel: NULL Pointer Dereference4.4—
    MediumCVE-2026-98930Linux Kernel: security vulnerability4.4—
    LowCVE-2026-98929Linux Kernel: security vulnerability3.0—
    Not ratedCVE-2026-98928Linux Kernel: security vulnerability——
    HighCVE-2026-98927Linux Kernel: security vulnerability7.0—
    MediumCVE-2026-98926Linux Kernel: security vulnerability4.7—
    LowCVE-2026-98925Linux Kernel: security vulnerability2.3—
    MediumCVE-2026-98924Linux Kernel: security vulnerability4.1—
    Not ratedCVE-2026-98923Linux Kernel: security vulnerability——
    Not ratedCVE-2026-98922Linux Kernel: NULL Pointer Dereference——
    Not ratedCVE-2026-98921Linux Kernel: Use-After-Free——
    Not ratedCVE-2026-98920Linux Kernel: security vulnerability——
    Not ratedCVE-2026-98919Linux Kernel: security vulnerability——
    Not ratedCVE-2026-98918Linux Kernel: security vulnerability——
    MediumCVE-2026-98917Linux Kernel: security vulnerability4.7—
    HighCVE-2026-98916Linux Kernel: security vulnerability7.1—
    HighCVE-2026-98915Linux Kernel: security vulnerability7.1—
    MediumCVE-2026-98914Linux Kernel: security vulnerability5.5—
    HighCVE-2026-98913Linux Kernel: security vulnerability7.1—
    LowCVE-2026-98912Linux Kernel: security vulnerability3.3—
    MediumCVE-2026-98911Linux Kernel: security vulnerability5.5—
    LowCVE-2026-98910Linux Kernel: security vulnerability3.3—
    MediumCVE-2026-98909Linux Kernel: security vulnerability5.5—
    LowCVE-2026-98908Linux Kernel: security vulnerability1.9—
    HighCVE-2026-98907Linux Kernel: security vulnerability7.1—
    MediumCVE-2026-98906Linux Kernel: security vulnerability4.1—
    MediumCVE-2026-98905Linux Kernel: security vulnerability5.5—
    HighCVE-2026-98904Linux Kernel: security vulnerability7.1—
    MediumCVE-2026-98903Linux Kernel: security vulnerability4.7—
    HighCVE-2026-98902Linux Kernel: security vulnerability7.1—
    MediumCVE-2026-98901Linux Kernel: security vulnerability5.4—
    HighCVE-2026-98900Linux Kernel: security vulnerability7.8—
    MediumCVE-2026-98899Linux Kernel: security vulnerability4.1—
    MediumCVE-2026-98898Linux Kernel: security vulnerability5.5—
    MediumCVE-2026-98897Linux Kernel: security vulnerability4.3—
    MediumCVE-2026-98896Linux Kernel: security vulnerability4.7—
    MediumCVE-2026-98895Linux Kernel: security vulnerability5.5—
    LowCVE-2026-98894Linux Kernel: security vulnerability3.3—
    MediumCVE-2026-98893Linux Kernel: security vulnerability5.5—
    MediumCVE-2026-98892Linux Kernel: security vulnerability5.5—
    MediumCVE-2026-98891Linux Kernel: security vulnerability4.3—
    MediumCVE-2026-98890Linux Kernel: security vulnerability5.5—
    HighCVE-2026-98889Linux Kernel: security vulnerability7.1—
    MediumCVE-2026-98888Linux Kernel: security vulnerability5.5—
    MediumCVE-2026-98887Linux Kernel: security vulnerability5.5—
    MediumCVE-2026-98886Linux Kernel: security vulnerability5.5—
    MediumCVE-2026-98885Linux Kernel: security vulnerability5.5—
    MediumCVE-2026-98884Linux Kernel: security vulnerability5.5—
    HighCVE-2026-98883Linux Kernel: security vulnerability7.1—
    HighCVE-2026-98882Linux Kernel: Buffer Overflow7.1—
    HighCVE-2026-98881Linux Kernel: security vulnerability7.1—
    MediumCVE-2026-98880Linux Kernel: security vulnerability5.5—
    MediumCVE-2026-98879Linux Kernel: security vulnerability5.5—
    MediumCVE-2026-98878Linux Kernel: Denial of Service5.5—
    MediumCVE-2026-98877Linux Kernel: NULL Pointer Dereference5.5—
    MediumCVE-2026-98876Linux Kernel: NULL Pointer Dereference5.5—
    MediumCVE-2026-98875Linux Kernel: security vulnerability5.5—
    LowCVE-2026-98874Linux Kernel: security vulnerability3.3—
    MediumCVE-2026-98873Linux Kernel: security vulnerability5.5—
    MediumCVE-2026-98872Linux Kernel: security vulnerability5.5—
    Not ratedCVE-2026-98871Linux Kernel: Deadlock——
    HighCVE-2026-98870Linux Kernel: Use-After-Free8.8—
    MediumCVE-2024-50169Linux Kernel: security vulnerability5.5—
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-98959
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-98959"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-98959.svg?lang=en" alt="CVE-2026-98959 – NEOSEC Intel" height="20"></a>