CVE-2024-48876
Vulnerability from cvelistv5
Published
2025-01-11 12:25
Modified
2025-01-20 06:19
Severity ?
EPSS score ?
0.03% (0.04028)
Summary
In the Linux kernel, the following vulnerability has been resolved: stackdepot: fix stack_depot_save_flags() in NMI context Per documentation, stack_depot_save_flags() was meant to be usable from NMI context if STACK_DEPOT_FLAG_CAN_ALLOC is unset. However, it still would try to take the pool_lock in an attempt to save a stack trace in the current pool (if space is available). This could result in deadlock if an NMI is handled while pool_lock is already held. To avoid deadlock, only try to take the lock in NMI context and give up if unsuccessful. The documentation is fixed to clearly convey this.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/031e04bdc834cda3b054ef6b698503b2b97e8186
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/9bfeeeff2c92b9dd261198b601b45bde4c529841
Impacted products
Vendor Product Version
Linux Linux Version: 4434a56ec20925333d6cf4d4093641d063abd35b
Version: 4434a56ec20925333d6cf4d4093641d063abd35b
 Create a notification for this product.
   Linux Linux Version: 6.8
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
   containers: {
      cna: {
         affected: [
            {
               defaultStatus: "unaffected",
               product: "Linux",
               programFiles: [
                  "include/linux/stackdepot.h",
                  "lib/stackdepot.c",
               ],
               repo: "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
               vendor: "Linux",
               versions: [
                  {
                     lessThan: "9bfeeeff2c92b9dd261198b601b45bde4c529841",
                     status: "affected",
                     version: "4434a56ec20925333d6cf4d4093641d063abd35b",
                     versionType: "git",
                  },
                  {
                     lessThan: "031e04bdc834cda3b054ef6b698503b2b97e8186",
                     status: "affected",
                     version: "4434a56ec20925333d6cf4d4093641d063abd35b",
                     versionType: "git",
                  },
               ],
            },
            {
               defaultStatus: "affected",
               product: "Linux",
               programFiles: [
                  "include/linux/stackdepot.h",
                  "lib/stackdepot.c",
               ],
               repo: "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
               vendor: "Linux",
               versions: [
                  {
                     status: "affected",
                     version: "6.8",
                  },
                  {
                     lessThan: "6.8",
                     status: "unaffected",
                     version: "0",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "6.12.*",
                     status: "unaffected",
                     version: "6.12.5",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "*",
                     status: "unaffected",
                     version: "6.13",
                     versionType: "original_commit_for_fix",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "In the Linux kernel, the following vulnerability has been resolved:\n\nstackdepot: fix stack_depot_save_flags() in NMI context\n\nPer documentation, stack_depot_save_flags() was meant to be usable from\nNMI context if STACK_DEPOT_FLAG_CAN_ALLOC is unset.  However, it still\nwould try to take the pool_lock in an attempt to save a stack trace in the\ncurrent pool (if space is available).\n\nThis could result in deadlock if an NMI is handled while pool_lock is\nalready held.  To avoid deadlock, only try to take the lock in NMI context\nand give up if unsuccessful.\n\nThe documentation is fixed to clearly convey this.",
            },
         ],
         providerMetadata: {
            dateUpdated: "2025-01-20T06:19:13.331Z",
            orgId: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            shortName: "Linux",
         },
         references: [
            {
               url: "https://git.kernel.org/stable/c/9bfeeeff2c92b9dd261198b601b45bde4c529841",
            },
            {
               url: "https://git.kernel.org/stable/c/031e04bdc834cda3b054ef6b698503b2b97e8186",
            },
         ],
         title: "stackdepot: fix stack_depot_save_flags() in NMI context",
         x_generator: {
            engine: "bippy-5f407fcff5a0",
         },
      },
   },
   cveMetadata: {
      assignerOrgId: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      assignerShortName: "Linux",
      cveId: "CVE-2024-48876",
      datePublished: "2025-01-11T12:25:17.819Z",
      dateReserved: "2025-01-09T09:51:32.384Z",
      dateUpdated: "2025-01-20T06:19:13.331Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      nvd: "{\"cve\":{\"id\":\"CVE-2024-48876\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-01-11T13:15:23.263\",\"lastModified\":\"2025-01-11T13:15:23.263\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nstackdepot: fix stack_depot_save_flags() in NMI context\\n\\nPer documentation, stack_depot_save_flags() was meant to be usable from\\nNMI context if STACK_DEPOT_FLAG_CAN_ALLOC is unset.  However, it still\\nwould try to take the pool_lock in an attempt to save a stack trace in the\\ncurrent pool (if space is available).\\n\\nThis could result in deadlock if an NMI is handled while pool_lock is\\nalready held.  To avoid deadlock, only try to take the lock in NMI context\\nand give up if unsuccessful.\\n\\nThe documentation is fixed to clearly convey this.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/031e04bdc834cda3b054ef6b698503b2b97e8186\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/9bfeeeff2c92b9dd261198b601b45bde4c529841\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}",
   },
}


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.