OESA-2023-1799 (CVE-2023-37453)

Vulnerability from osv_openeuler – Published: 2023-11-10 11:06 – Updated: 2026-08-06 11:06 – Source website
VLAI
Summary
kernel security update
Details

The Linux Kernel, the operating system core itself.

Security Fix(es):

An issue was discovered in the USB subsystem in the Linux kernel through 6.4.2. There is an out-of-bounds and crash in read_descriptors in drivers/usb/core/sysfs.c.(CVE-2023-37453)

An issue was discovered in the Linux kernel before 6.5.9, exploitable by local users with userspace access to MMIO registers. Incorrect access checking in the #VC handler and instruction emulation of the SEV-ES emulation of MMIO accesses could lead to arbitrary write access to kernel memory (and thus privilege escalation). This depends on a race condition through which userspace can replace an instruction before the #VC handler reads it.(CVE-2023-46813)

An issue was discovered in the Linux kernel through 6.5.9. During a race with SQ thread exit, an io_uring/fdinfo.c io_uring_show_fdinfo NULL pointer dereference can occur.(CVE-2023-46862)

A use-after-free vulnerability was found in drivers/nvme/target/tcp.cinnvmet_tcp_free_crypto` due to a logical bug in the NVMe-oF/TCP subsystem in the Linux kernel. This issue may allow a malicious user to cause a use-after-free and double-free problem, which may permit remote code execution or lead to local privilege escalation in case that the attacker already has local privileges.(CVE-2023-5178)

Severity
7.8 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
References
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "aarch64": [
          "kernel-source-5.10.0-153.32.0.109.oe2203sp2.aarch64.rpm",
          "python3-perf-debuginfo-5.10.0-153.32.0.109.oe2203sp2.aarch64.rpm",
          "perf-debuginfo-5.10.0-153.32.0.109.oe2203sp2.aarch64.rpm",
          "kernel-devel-5.10.0-153.32.0.109.oe2203sp2.aarch64.rpm",
          "kernel-headers-5.10.0-153.32.0.109.oe2203sp2.aarch64.rpm",
          "bpftool-5.10.0-153.32.0.109.oe2203sp2.aarch64.rpm",
          "kernel-debugsource-5.10.0-153.32.0.109.oe2203sp2.aarch64.rpm",
          "kernel-tools-devel-5.10.0-153.32.0.109.oe2203sp2.aarch64.rpm",
          "kernel-tools-5.10.0-153.32.0.109.oe2203sp2.aarch64.rpm",
          "kernel-tools-debuginfo-5.10.0-153.32.0.109.oe2203sp2.aarch64.rpm",
          "kernel-debuginfo-5.10.0-153.32.0.109.oe2203sp2.aarch64.rpm",
          "kernel-5.10.0-153.32.0.109.oe2203sp2.aarch64.rpm",
          "bpftool-debuginfo-5.10.0-153.32.0.109.oe2203sp2.aarch64.rpm",
          "python3-perf-5.10.0-153.32.0.109.oe2203sp2.aarch64.rpm",
          "perf-5.10.0-153.32.0.109.oe2203sp2.aarch64.rpm"
        ],
        "src": [
          "kernel-5.10.0-153.32.0.109.oe2203sp2.src.rpm"
        ],
        "x86_64": [
          "perf-debuginfo-5.10.0-153.32.0.109.oe2203sp2.x86_64.rpm",
          "kernel-tools-devel-5.10.0-153.32.0.109.oe2203sp2.x86_64.rpm",
          "perf-5.10.0-153.32.0.109.oe2203sp2.x86_64.rpm",
          "kernel-tools-5.10.0-153.32.0.109.oe2203sp2.x86_64.rpm",
          "bpftool-debuginfo-5.10.0-153.32.0.109.oe2203sp2.x86_64.rpm",
          "kernel-devel-5.10.0-153.32.0.109.oe2203sp2.x86_64.rpm",
          "kernel-5.10.0-153.32.0.109.oe2203sp2.x86_64.rpm",
          "kernel-debuginfo-5.10.0-153.32.0.109.oe2203sp2.x86_64.rpm",
          "kernel-source-5.10.0-153.32.0.109.oe2203sp2.x86_64.rpm",
          "kernel-tools-debuginfo-5.10.0-153.32.0.109.oe2203sp2.x86_64.rpm",
          "python3-perf-5.10.0-153.32.0.109.oe2203sp2.x86_64.rpm",
          "kernel-headers-5.10.0-153.32.0.109.oe2203sp2.x86_64.rpm",
          "kernel-debugsource-5.10.0-153.32.0.109.oe2203sp2.x86_64.rpm",
          "python3-perf-debuginfo-5.10.0-153.32.0.109.oe2203sp2.x86_64.rpm",
          "bpftool-5.10.0-153.32.0.109.oe2203sp2.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:22.03-LTS-SP2",
        "name": "kernel",
        "purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-22.03-LTS-SP2"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.10.0-153.32.0.109.oe2203sp2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "severity": "High"
  },
  "details": "The Linux Kernel, the operating system core itself.\r\n\r\n\r\n\r\nSecurity Fix(es):\r\n\r\nAn issue was discovered in the USB subsystem in the Linux kernel through 6.4.2. There is an out-of-bounds and crash in read_descriptors in drivers/usb/core/sysfs.c.(CVE-2023-37453)\r\n\r\nAn issue was discovered in the Linux kernel before 6.5.9, exploitable by local users with userspace access to MMIO registers. Incorrect access checking in the #VC handler and instruction emulation of the SEV-ES emulation of MMIO accesses could lead to arbitrary write access to kernel memory (and thus privilege escalation). This depends on a race condition through which userspace can replace an instruction before the #VC handler reads it.(CVE-2023-46813)\r\n\r\nAn issue was discovered in the Linux kernel through 6.5.9. During a race with SQ thread exit, an io_uring/fdinfo.c io_uring_show_fdinfo NULL pointer dereference can occur.(CVE-2023-46862)\r\n\r\nA use-after-free vulnerability was found in drivers/nvme/target/tcp.c` in `nvmet_tcp_free_crypto` due to a logical bug in the NVMe-oF/TCP subsystem in the Linux kernel. This issue may allow a malicious user to cause a use-after-free and double-free problem, which may permit remote code execution or lead to local privilege escalation in case that the attacker already has local privileges.(CVE-2023-5178)",
  "id": "OESA-2023-1799",
  "modified": "2026-08-06T11:06:14Z",
  "published": "2023-11-10T11:06:14Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1799"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-37453"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-46813"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-46862"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-5178"
    }
  ],
  "schema_version": "1.7.2",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "kernel security update",
  "upstream": [
    "CVE-2023-37453",
    "CVE-2023-46813",
    "CVE-2023-46862",
    "CVE-2023-5178"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.