HighCVE-2023-52909

    Linux Kernel: Mehrere Schwachstellen

    Published Sources: BSI

    Share

    What is affected, what to do

    In the Linux kernel, the following vulnerability has been resolved: nfsd: fix handling of cached open files in nfsd4_open codepath Commit fb70bf124b05 ("NFSD: Instantiate a struct file when creating a regular NFSv4 file") added the ability to cache an open fd over a compound. There are a couple of problems with the way this currently works: It's racy, as a newly-created nfsd_file can end up with its PENDING bit cleared while the nf is hashed, and the nf_file pointer is still zeroed out.

    Update Linux Kernel to version 6.1.7, Linux Kernel to version 6.2.

    Affected
    • Linux Kernel lt 5.19..6.1.7
    Fixed in
    • Linux Kernel 6.1.7
    • Linux Kernel 6.2

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

    Metrics

    7.5

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.5

    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 51.3

    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
    54.53 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.5 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.5
    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
    51.3
    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
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 10 September 2024

    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: nfsd: fix handling of cached open files in nfsd4_open codepath Commit fb70bf124b05 ("NFSD: Instantiate a struct file when creating a regular NFSv4 file") added the ability to cache an open fd over a compound. There are a couple of problems with the way this currently works: It's racy, as a newly-created nfsd_file can end up with its PENDING bit cleared while the nf is hashed, and the nf_file pointer is still zeroed out. Other tasks can find it in this state and they expect to see a valid nf_file, and can oops if nf_file is NULL. Also, there is no guarantee that we'll end up creating a new nfsd_file if one is already in the hash. If an extant entry is in the hash with a valid nf_file, nfs4_get_vfs_file will clobber its nf_file pointer with the value of op_file and the old nf_file will leak. Fix both issues by making a new nfsd_file_acquirei_opened variant that takes an optional file pointer. If one is present when this is called, we'll take a new reference to it instead of trying to open the file. If the nfsd_file already has a valid nf_file, we'll just ignore the optional file and pass the nfsd_file back as-is. Also rework the tracepoints a bit to allow for an "opened" variant and don't try to avoid counting acquisitions in the case where we already have a cached open file.

    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.18 – < 4.19.320
    • 2.6.30 – < 4.14.304
    • 2.6.36 – < 5.10.165
    • 3.0 – < 4.14.304
    • 3.1 – < 4.14.303
    • 3.15 – < 4.14.304
    • 3.17 – < 4.14.303
    • 3.18 – < 5.10.238
    • 3.9 – < 5.4.282
    • 4.10 – < 4.19.320
    • 4.12 – < 4.19.320
    • 4.13.16 – < 4.14
    • 4.14 – < 6.1.113
    • 4.15 – < 4.19.270
    • 4.15 – < 4.19.271
    • 4.16 – < 6.1.191
    • 4.17 – < 4.19.271
    • 4.19 – < 4.19.320
    • 4.19.142 – < 4.19.270
    • 4.20 – < 5.4.229
    • 4.20 – < 5.4.230
    • 4.20 – < 5.4.282
    • 4.20 – < 6.1.7
    • 4.4 – < 4.19.270
    • 4.9 – < 4.14.304
    • 5.0 – < 5.4.229
    • 5.1 – < 5.10.165
    • 5.1 – < 5.4.230
    • 5.1 – < 5.4.282
    • 5.10 – < 5.10.164
    • 5.10 – < 5.15.171
    • 5.10.99 – < 5.10.165
    • 5.11 – < 5.15.165
    • 5.11 – < 5.15.181
    • 5.11 – < 5.15.89
    • 5.11 – < 5.15.90
    • 5.12 – < 5.15.89
    • 5.12 – < 5.15.90
    • 5.14 – < 5.15.165
    • 5.15 – < 5.15.89
    • 5.15 – < 5.15.90
    • 5.15 – < 6.1.7
    • 5.15.152 – < 5.15.168
    • 5.15.153 – < 5.15.165
    • 5.15.22 – < 5.15.90
    • 5.15.84 – < 5.15.165
    • 5.1.6 – < 5.2
    • 5.16 – < 6.1.103
    • 4.19.320
    • 4.14.304
    • 5.10.165
    • 4.14.304
    • 4.14.303
    • 4.14.304
    • 4.14.303
    • 5.10.238
    • 5.4.282
    • 4.19.320
    • 4.19.320
    • 4.14
    • 6.1.113
    • 4.19.270
    • 4.19.271
    • 6.1.191
    • 4.19.271
    • 4.19.320
    • 4.19.270
    • 5.4.229
    • 5.4.230
    • 5.4.282
    • 6.1.7
    • 4.19.270
    • 4.14.304
    • 5.4.229
    • 5.10.165
    • 5.4.230
    • 5.4.282
    • 5.10.164
    • 5.15.171
    • 5.10.165
    • 5.15.165
    • 5.15.181
    • 5.15.89
    • 5.15.90
    • 5.15.89
    • 5.15.90
    • 5.15.165
    • 5.15.89
    • 5.15.90
    • 6.1.7
    • 5.15.168
    • 5.15.165
    • 5.15.90
    • 5.15.165
    • 5.2
    • 6.1.103
    From bundled advisories, not CVE-specific (2)

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

    Products from bundled advisories
    Affected versionsFixed in
    DellPowerScale OneFS
    • < 4.0.33
    • 4.0.33
    IBMDataPower Gateway
    • < 10.6.6.0
    • 10.6.6.0

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebianlinuxbookworm
    Linuxdebianlinuxbullseye
    Linuxdebianlinux-6.1bullseye
    Linuxubuntulinux-nvidia-tegranoble
    Linuxlinuxlinux_kernel6.1.7
    Linuxlinuxlinux_kernel6.1
    Linuxlinuxlinux_kernel6.2
    Linuxlinuxlinux_kernel—
    Linuxlinuxlinux_kernel6.11

    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:N/I:N/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:N/I:N/A:H

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

    Linked CVEs

    Linked CVEs
    HighCVE-2024-43882Linux Kernel: Time-of-check Time-of-use (TOCTOU) Race Condition8.4—
    HighCVE-2024-43881Linux Kernel: security vulnerability8.8—
    HighCVE-2024-43880Linux Kernel: security vulnerability7.8—
    MediumCVE-2024-43879Linux Kernel: security vulnerability5.5—
    HighCVE-2024-43878Linux Kernel: security vulnerability8.1—
    HighCVE-2024-43877Linux Kernel: security vulnerability7.8—
    MediumCVE-2024-43876Linux Kernel: security vulnerability5.5—
    MediumCVE-2024-43875Linux Kernel: security vulnerability5.5—
    MediumCVE-2024-43874Linux Kernel: NULL Pointer Dereference5.5—
    HighCVE-2024-43873Linux Kernel: security vulnerability7.8—
    HighCVE-2024-43872Linux Kernel: security vulnerability7.5—
    MediumCVE-2024-43871Linux Kernel: Memory Leak5.5—
    MediumCVE-2024-43870Linux Kernel: security vulnerability5.5—
    MediumCVE-2024-43869Linux Kernel: security vulnerability5.5—
    MediumCVE-2024-43868Linux Kernel: security vulnerability5.5—
    MediumCVE-2024-43867Linux Kernel: security vulnerability5.5—
    MediumCVE-2024-43866Linux Kernel: security vulnerability4.7—
    MediumCVE-2024-43865Linux Kernel: security vulnerability5.5—
    CriticalCVE-2024-43864Linux Kernel: security vulnerability9.8—
    MediumCVE-2024-43863Linux Kernel: Deadlock5.5—
    MediumCVE-2024-43862Linux Kernel: Deadlock5.5—
    MediumCVE-2024-43861Linux Kernel: Memory Leak5.5—
    MediumCVE-2023-52914Linux Kernel: security vulnerability5.5—
    HighCVE-2023-52913Linux Kernel: security vulnerability7.8—
    Show 53 more CVEs
    Linked CVEs
    MediumCVE-2023-52912Linux Kernel: security vulnerability5.5—
    MediumCVE-2023-52911Linux Kernel: NULL Pointer Dereference5.5—
    HighCVE-2023-52910Linux Kernel: security vulnerability8.8—
    HighCVE-2023-52909Linux Kernel: security vulnerability7.5—
    MediumCVE-2023-52908Linux Kernel: security vulnerability5.5—
    HighCVE-2023-52907Linux Kernel: Use-After-Free7.8—
    HighCVE-2023-52906Linux Kernel: security vulnerability7.8—
    MediumCVE-2023-52905Linux Kernel: security vulnerability5.5—
    MediumCVE-2023-52904Linux Kernel: NULL Pointer Dereference5.5—
    HighCVE-2023-52903Linux Kernel: security vulnerability7.8—
    MediumCVE-2023-52902Linux Kernel: Memory Leak5.5—
    MediumCVE-2023-52901Linux Kernel: NULL Pointer Dereference5.5—
    MediumCVE-2023-52900Linux Kernel: NULL Pointer Dereference5.5—
    MediumCVE-2023-52899Linux Kernel: NULL Pointer Dereference5.5—
    MediumCVE-2023-52898Linux Kernel: NULL Pointer Dereference4.7—
    MediumCVE-2023-52897Linux Kernel: security vulnerability4.7—
    MediumCVE-2023-52896Linux Kernel: NULL Pointer Dereference4.7—
    MediumCVE-2023-52895Linux Kernel: security vulnerability5.5—
    MediumCVE-2023-52894Linux Kernel: NULL Pointer Dereference5.5—
    MediumCVE-2023-52893Linux Kernel: security vulnerability5.5—
    HighCVE-2022-48899Linux Kernel: Use-After-Free7.8—
    MediumCVE-2022-48898Linux Kernel: Race Condition4.7—
    MediumCVE-2022-48897Linux Kernel: security vulnerability5.5—
    MediumCVE-2022-48896Linux Kernel: Memory Leak5.5—
    MediumCVE-2022-48895Linux Kernel: NULL Pointer Dereference5.5—
    MediumCVE-2022-48894Linux Kernel: NULL Pointer Dereference5.5—
    MediumCVE-2022-48893Linux Kernel: security vulnerability5.5—
    HighCVE-2022-48892Linux Kernel: Use-After-Free7.8—
    MediumCVE-2022-48891Linux Kernel: security vulnerability5.5—
    MediumCVE-2022-48890Linux Kernel: Memory Leak5.5—
    MediumCVE-2022-48889Linux Kernel: security vulnerability5.5—
    MediumCVE-2022-48888Linux Kernel: Memory Leak5.5—
    HighCVE-2022-48887Linux Kernel: security vulnerability7.8—
    MediumCVE-2022-48886Linux Kernel: NULL Pointer Dereference5.5—
    MediumCVE-2022-48885Linux Kernel: Memory Leak5.5—
    MediumCVE-2022-48884Linux Kernel: security vulnerability5.5—
    HighCVE-2022-48883Linux Kernel: security vulnerability7.8—
    MediumCVE-2022-48882Linux Kernel: security vulnerability5.5—
    HighCVE-2022-48881Linux Kernel: Memory Leak7.1—
    MediumCVE-2022-48880Linux Kernel: security vulnerability5.5—
    MediumCVE-2022-48879Linux Kernel: security vulnerability5.5—
    HighCVE-2022-48878Linux Kernel: Use-After-Free7.8—
    Not ratedCVE-2022-48877Vulnerability CVE-2022-488770.0—
    MediumCVE-2022-48876Linux Kernel: NULL Pointer Dereference5.5—
    MediumCVE-2022-48875Linux Kernel: security vulnerability5.5—
    HighCVE-2022-48874Linux Kernel: Use-After-Free7.8—
    HighCVE-2022-48873Linux Kernel: Use-After-Free7.8—
    HighCVE-2022-48872Linux Kernel: Use-After-Free7.8—
    HighCVE-2022-48871Linux Kernel: Out-of-Bounds Access8.8—
    MediumCVE-2022-48870Linux Kernel: NULL Pointer Dereference5.5—
    MediumCVE-2022-48869Linux Kernel: Use-After-Free4.7—
    MediumCVE-2022-48868Linux Kernel: NULL Pointer Dereference5.5—
    HighCVE-2022-48867Linux Kernel: Use-After-Free7.8—
    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-2023-52909
    <a href="https://intel.neosec.eu/en/cve/CVE-2023-52909"><img src="https://intel.neosec.eu/badge/cve/CVE-2023-52909.svg?lang=en" alt="CVE-2023-52909 – NEOSEC Intel" height="20"></a>