ghsa-8j9g-23ch-xjq9
Vulnerability from github
Published
2024-05-01 15:30
Modified
2024-12-23 21:30
Severity ?
5.5 (Medium) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Details

In the Linux kernel, the following vulnerability has been resolved:

net: phy: fix phy_get_internal_delay accessing an empty array

The phy_get_internal_delay function could try to access to an empty array in the case that the driver is calling phy_get_internal_delay without defining delay_values and rx-internal-delay-ps or tx-internal-delay-ps is defined to 0 in the device-tree. This will lead to "unable to handle kernel NULL pointer dereference at virtual address 0". To avoid this kernel oops, the test should be delay

= 0. As there is already delay < 0 test just before, the test could only be size == 0.

Show details on source website

To clipboard 

{
   affected: [],
   aliases: [
      "CVE-2024-27047",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-476",
      ],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2024-05-01T13:15:49Z",
      severity: "MODERATE",
   },
   details: "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: fix phy_get_internal_delay accessing an empty array\n\nThe phy_get_internal_delay function could try to access to an empty\narray in the case that the driver is calling phy_get_internal_delay\nwithout defining delay_values and rx-internal-delay-ps or\ntx-internal-delay-ps is defined to 0 in the device-tree.\nThis will lead to \"unable to handle kernel NULL pointer dereference at\nvirtual address 0\". To avoid this kernel oops, the test should be delay\n>= 0. As there is already delay < 0 test just before, the test could\nonly be size == 0.",
   id: "GHSA-8j9g-23ch-xjq9",
   modified: "2024-12-23T21:30:51Z",
   published: "2024-05-01T15:30:35Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2024-27047",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/0307cf443308ecc6be9b2ca312bb31bae5e5a7ad",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/06dd21045a7e8bc8701b0ebedcd9a30a6325878b",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/0e939a002c8a7d66e60bd0ea6b281fb39d713c1a",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/2a2ff709511617de9c6c072eeee82bcbbdfecaf8",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/4469c0c5b14a0919f5965c7ceac96b523eb57b79",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/589ec16174dd9378953b8232ae76fad0a96e1563",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/c0691de7df1d51482a52cac93b7fe82fd9dd296b",
      },
      {
         type: "WEB",
         url: "https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
         type: "CVSS_V3",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.