ghsa-v9r3-3hjw-wxm2
Vulnerability from github
Published
2024-07-29 18:30
Modified
2024-08-26 15:31
Details

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

net/dpaa2: Avoid explicit cpumask var allocation on stack

For CONFIG_CPUMASK_OFFSTACK=y kernel, explicit allocation of cpumask variable on stack is not recommended since it can cause potential stack overflow.

Instead, kernel code should always use *cpumask_var API(s) to allocate cpumask var in config-neutral way, leaving allocation strategy to CONFIG_CPUMASK_OFFSTACK.

Use *cpumask_var API(s) to address it.

Show details on source website


{
   affected: [],
   aliases: [
      "CVE-2024-42093",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-787",
      ],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2024-07-29T18:15:11Z",
      severity: "HIGH",
   },
   details: "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/dpaa2: Avoid explicit cpumask var allocation on stack\n\nFor CONFIG_CPUMASK_OFFSTACK=y kernel, explicit allocation of cpumask\nvariable on stack is not recommended since it can cause potential stack\noverflow.\n\nInstead, kernel code should always use *cpumask_var API(s) to allocate\ncpumask var in config-neutral way, leaving allocation strategy to\nCONFIG_CPUMASK_OFFSTACK.\n\nUse *cpumask_var API(s) to address it.",
   id: "GHSA-v9r3-3hjw-wxm2",
   modified: "2024-08-26T15:31:14Z",
   published: "2024-07-29T18:30:43Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2024-42093",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/48147337d7efdea6ad6e49f5b8eb894b95868ef0",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/5e4f25091e6d06e99a23f724c839a58a8776a527",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/69f49527aea12c23b78fb3d0a421950bf44fb4e2",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/763896ab62a672d728f5eb10ac90d98c607a8509",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/a55afc0f5f20ba30970aaf7271929dc00eee5e7d",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/b2262b3be27cee334a2fa175ae3afb53f38fb0b1",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/d33fe1714a44ff540629b149d8fab4ac6967585c",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.


Loading…

Loading…

Loading…

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.