MediumCVE-2026-98657

    Linux Kernel: security vulnerability (CVE-2026-98657)

    Published Last modified Sources: Debian LTS, Msrc Update Guide, CVE.org, BSI

    What is affected, what to do

    In the Linux kernel, the following vulnerability has been resolved: iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure pm_runtime_set_active() failing in probe() jumps to error_unreg_buffer, which only calls iio_triggered_buffer_cleanup() -- it does not undo the iio_device_register() that already succeeded a few lines above. probe() then returns the error, the devm-managed indio_dev is freed, but the iio core still has it registered: the sysfs/chardev nodes stay live and point at freed memory. Add an error_unreg_dev label that unregisters the iio device before falling through to the existing buffer cleanup, mirroring the teardown order already used in lidar_remove().

    Update Linux Kernel to version 5.10.273, Linux Kernel to version 5.15.224, Linux Kernel to version 6.1.191.

    Affected
    • Linux Kernel lt 4.5..5.10.273
    • Linux Kernel lt 5.11..5.15.224
    • Linux Kernel lt 5.16..6.1.191
    • Linux Kernel lt 6.2..6.6.160
    • Linux Kernel lt 6.7..6.12.113
    • Linux Kernel lt 6.13..6.18.56
    • Linux Kernel lt 6.19..7.2.10
    Fixed in
    • Linux Kernel 5.10.273
    • Linux Kernel 5.15.224
    • Linux Kernel 6.1.191
    • Linux Kernel 6.6.160
    • Linux Kernel 6.12.113
    • Linux Kernel 6.18.56
    • Linux Kernel 7.2.10
    • Linux Kernel 7.3

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

    Metrics

    5.2

    Priority

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

    Source: Vendor (CNA), CVSS v3

    5.2

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: Debian LTS, Msrc Update Guide, CVE.org, BSI

    0.2 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 7.2

    Show all metrics
    Severity
    Medium
    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
    56.41 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
    5.2 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
    5.2
    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.2 %
    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
    7.2
    Low — this CVE sits in the lower 10% of all CVEs scored today.
    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
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    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: iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure pm_runtime_set_active() failing in probe() jumps to error_unreg_buffer, which only calls iio_triggered_buffer_cleanup() -- it does not undo the iio_device_register() that already succeeded a few lines above. probe() then returns the error, the devm-managed indio_dev is freed, but the iio core still has it registered: the sysfs/chardev nodes stay live and point at freed memory. Add an error_unreg_dev label that unregisters the iio device before falling through to the existing buffer cleanup, mirroring the teardown order already used in lidar_remove().

    Source: Debian LTS Advisories, Microsoft Security Update Guide, cvelistv5, NVD (NIST), BSI WID Portal, BSI CSAF

    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
    • 4.5 – < 5.10.273
    • 5.11 – < 5.15.224
    • 5.16 – < 6.1.191
    • 6.13 – < 6.18.56
    • 6.19 – < 7.2.10
    • 6.7 – < 6.12.113
    • —
    • 6.2 – < 6.6.160
    • 5.10.273
    • 5.15.224
    • 6.1.191
    • 6.18.56
    • 7.2.10
    • 6.12.113
    • 7.3
    • 6.6.160

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebianlinux-6.12bookworm

    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

      Show 4 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Affected versions (publisher)added
      —
      Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/98xxx/CVE-2026-98657.json">CVE-2026-98657</a>
      Referenceadded
      —
      https://git.kernel.org/stable/c/4a564e39cb99234e8c5b0a39aa30edcc8cf4cf1b
      Referenceadded
      —
      https://git.kernel.org/stable/c/58e68e5272a319fff4a704df1ac41e9e3c69587c
      Referenceadded
      —
      https://git.kernel.org/stable/c/93ecee9ff3af4c2b482fdd4ec98c3308e8dd23a6

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

    2. Record modifiedLinux

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Affected versions (publisher)added
      —
      Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/98xxx/CVE-2026-98657.json">CVE-2026-98657</a>
      Referenceadded
      —
      https://git.kernel.org/stable/c/2c8211eef98929c5188f8c2224e83b9a63b41bd1

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

    3. Record modifiedLinux

      1 individual change: Affected versions (publisher)

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Affected versions (publisher)added
      —
      Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/98xxx/CVE-2026-98657.json">CVE-2026-98657</a>

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

    4. ReceivedLinux

      Description added or changed

      Show 6 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      In the Linux kernel, the following vulnerability has been resolved: iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure pm_runtime_set_active() failing in probe() jumps to error_unreg_buffer, which only calls iio_triggered_buffer_cleanup() -- it does not undo the iio_device_register() that already succeeded a few lines above. probe() then returns the error, the devm-managed indio_dev is freed, but the iio core still has it registered: the sysfs/chardev nodes stay live and point at freed memory. Add an error_unreg_dev label that unregisters the iio device before falling through to the existing buffer cleanup, mirroring the teardown order already used in lidar_remove().
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/98xxx/CVE-2026-98657.json">CVE-2026-98657</a>
      Referenceadded
      —
      https://git.kernel.org/stable/c/06fa13c53442257b94ea1519555ceddaaea57e0d
      Referenceadded
      —
      https://git.kernel.org/stable/c/20ebd7f4e35c0a737f011bc83aeb0cdd37507648
      Referenceadded
      —
      https://git.kernel.org/stable/c/4daa9ca557b4b98ae1ad38a6d1deaa3e31eb8edf
      Referenceadded
      —
      https://git.kernel.org/stable/c/e462b47b9637b8c0285f4a38b5af9a322847d164

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

    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-98657
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-98657"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-98657.svg?lang=en" alt="CVE-2026-98657 – NEOSEC Intel" height="20"></a>