USN-6572-1

Vulnerability from osv_ubuntu – Published: 2024-01-09 18:04 – Updated: 2024-01-09 18:04 – Source website
VLAI
Summary
linux-azure vulnerabilities
Details

Yu Hao discovered that the UBI driver in the Linux kernel did not properly check for MTD with zero erasesize during device attachment. A local privileged attacker could use this to cause a denial of service (system crash). (CVE-2023-31085)

Bien Pham discovered that the netfiler subsystem in the Linux kernel contained a race condition, leading to a use-after-free vulnerability. A local user could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2023-4244)

Maxim Levitsky discovered that the KVM nested virtualization (SVM) implementation for AMD processors in the Linux kernel did not properly handle x2AVIC MSRs. An attacker in a guest VM could use this to cause a denial of service (host kernel crash). (CVE-2023-5090)

It was discovered that the SMB network file sharing protocol implementation in the Linux kernel did not properly handle certain error conditions, leading to a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2023-5345)

Murray McAllister discovered that the VMware Virtual GPU DRM driver in the Linux kernel did not properly handle memory objects when storing surfaces, leading to a use-after-free vulnerability. A local attacker in a guest VM could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2023-5633)

Impacted products
Ecosystem Package Version
Ubuntu:23.10 linux-azure
pkg:deb/ubuntu/linux-azure@6.5.0-1009.9?arch=source&distro=mantic
Affected: < 6.5.0-1009.9 (ecosystem)
6.2.0-1003.36.2.0-1004.46.5.0-1004.46.5.0-1006.66.5.0-1007.76.5.0-1008.8

{
  "affected": [
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "linux-azure-cloud-tools-6.5.0-1009",
            "binary_version": "6.5.0-1009.9"
          },
          {
            "binary_name": "linux-azure-headers-6.5.0-1009",
            "binary_version": "6.5.0-1009.9"
          },
          {
            "binary_name": "linux-azure-tools-6.5.0-1009",
            "binary_version": "6.5.0-1009.9"
          },
          {
            "binary_name": "linux-buildinfo-6.5.0-1009-azure",
            "binary_version": "6.5.0-1009.9"
          },
          {
            "binary_name": "linux-cloud-tools-6.5.0-1009-azure",
            "binary_version": "6.5.0-1009.9"
          },
          {
            "binary_name": "linux-headers-6.5.0-1009-azure",
            "binary_version": "6.5.0-1009.9"
          },
          {
            "binary_name": "linux-image-unsigned-6.5.0-1009-azure",
            "binary_version": "6.5.0-1009.9"
          },
          {
            "binary_name": "linux-image-unsigned-6.5.0-1009-azure-dbgsym",
            "binary_version": "6.5.0-1009.9"
          },
          {
            "binary_name": "linux-modules-6.5.0-1009-azure",
            "binary_version": "6.5.0-1009.9"
          },
          {
            "binary_name": "linux-modules-extra-6.5.0-1009-azure",
            "binary_version": "6.5.0-1009.9"
          },
          {
            "binary_name": "linux-modules-iwlwifi-6.5.0-1009-azure",
            "binary_version": "6.5.0-1009.9"
          },
          {
            "binary_name": "linux-tools-6.5.0-1009-azure",
            "binary_version": "6.5.0-1009.9"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:23.10",
        "name": "linux-azure",
        "purl": "pkg:deb/ubuntu/linux-azure@6.5.0-1009.9?arch=source\u0026distro=mantic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.5.0-1009.9"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.2.0-1003.3",
        "6.2.0-1004.4",
        "6.5.0-1004.4",
        "6.5.0-1006.6",
        "6.5.0-1007.7",
        "6.5.0-1008.8"
      ]
    }
  ],
  "aliases": [],
  "details": "Yu Hao discovered that the UBI driver in the Linux kernel did not properly\ncheck for MTD with zero erasesize during device attachment. A local\nprivileged attacker could use this to cause a denial of service (system\ncrash). (CVE-2023-31085)\n\nBien Pham discovered that the netfiler subsystem in the Linux kernel\ncontained a race condition, leading to a use-after-free vulnerability. A\nlocal user could use this to cause a denial of service (system crash) or\npossibly execute arbitrary code. (CVE-2023-4244)\n\nMaxim Levitsky discovered that the KVM nested virtualization (SVM)\nimplementation for AMD processors in the Linux kernel did not properly\nhandle x2AVIC MSRs. An attacker in a guest VM could use this to cause a\ndenial of service (host kernel crash). (CVE-2023-5090)\n\nIt was discovered that the SMB network file sharing protocol implementation\nin the Linux kernel did not properly handle certain error conditions,\nleading to a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2023-5345)\n\nMurray McAllister discovered that the VMware Virtual GPU DRM driver in the\nLinux kernel did not properly handle memory objects when storing surfaces,\nleading to a use-after-free vulnerability. A local attacker in a guest VM\ncould use this to cause a denial of service (system crash) or possibly\nexecute arbitrary code. (CVE-2023-5633)\n\n",
  "id": "USN-6572-1",
  "modified": "2024-01-09T18:04:06.463651Z",
  "published": "2024-01-09T18:04:06.463651Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://ubuntu.com/security/notices/USN-6572-1"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2023-4244"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2023-5090"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2023-5345"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2023-5633"
    },
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2023-31085"
    }
  ],
  "related": [
    "CVE-2023-4244",
    "UBUNTU-CVE-2023-4244",
    "CVE-2023-5090",
    "UBUNTU-CVE-2023-5090",
    "CVE-2023-5345",
    "UBUNTU-CVE-2023-5345",
    "CVE-2023-5633",
    "UBUNTU-CVE-2023-5633",
    "CVE-2023-31085",
    "UBUNTU-CVE-2023-31085"
  ],
  "schema_version": "1.6.3",
  "summary": "linux-azure vulnerabilities"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    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.