ghsa-c5xm-9r44-7w3j
Vulnerability from github
Published
2024-10-21 15:32
Modified
2024-10-23 18:33
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:

padata: use integer wrap around to prevent deadlock on seq_nr overflow

When submitting more than 2^32 padata objects to padata_do_serial, the current sorting implementation incorrectly sorts padata objects with overflowed seq_nr, causing them to be placed before existing objects in the reorder list. This leads to a deadlock in the serialization process as padata_find_next cannot match padata->seq_nr and pd->processed because the padata instance with overflowed seq_nr will be selected next.

To fix this, we use an unsigned integer wrap around to correctly sort padata objects in scenarios with integer overflow.

Show details on source website

To clipboard 

{
   affected: [],
   aliases: [
      "CVE-2024-47739",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-190",
      ],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2024-10-21T13:15:04Z",
      severity: "MODERATE",
   },
   details: "In the Linux kernel, the following vulnerability has been resolved:\n\npadata: use integer wrap around to prevent deadlock on seq_nr overflow\n\nWhen submitting more than 2^32 padata objects to padata_do_serial, the\ncurrent sorting implementation incorrectly sorts padata objects with\noverflowed seq_nr, causing them to be placed before existing objects in\nthe reorder list. This leads to a deadlock in the serialization process\nas padata_find_next cannot match padata->seq_nr and pd->processed\nbecause the padata instance with overflowed seq_nr will be selected\nnext.\n\nTo fix this, we use an unsigned integer wrap around to correctly sort\npadata objects in scenarios with integer overflow.",
   id: "GHSA-c5xm-9r44-7w3j",
   modified: "2024-10-23T18:33:07Z",
   published: "2024-10-21T15:32:26Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2024-47739",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/1b8cf11b3ca593a8802a51802cd0c28c38501428",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/1bd712de96ad7167fe0d608e706cd60587579f16",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/46c4079460f4dcaf445860679558eedef4e1bc91",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/72164d5b648951684b1a593996b37a6083c61d7d",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/9a22b2812393d93d84358a760c347c21939029a6",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/9e279e6c1f012b82628b89e1b9c65dbefa8ca25a",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/ab205e1c3846326f162180e56825b4ba38ce9c30",
      },
   ],
   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.