fkie_cve-2025-21641
Vulnerability from fkie_nvd
Published
2025-01-19 11:15
Modified
2025-01-19 11:15
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: mptcp: sysctl: blackhole timeout: avoid using current->nsproxy As mentioned in the previous commit, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info from the reader's/writer's netns vs only from the opener's netns. - current->nsproxy can be NULL in some cases, resulting in an 'Oops' (null-ptr-deref), e.g. when the current task is exiting, as spotted by syzbot [1] using acct(2). The 'pernet' structure can be obtained from the table->data using container_of().
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/4c74fbdc5ab95b13945be01e6065940b68222db7
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/92cf7a51bdae24a32c592adcdd59a773ae149289
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: sysctl: blackhole timeout: avoid using current-\u003ensproxy\n\nAs mentioned in the previous commit, using the \u0027net\u0027 structure via\n\u0027current\u0027 is not recommended for different reasons:\n\n- Inconsistency: getting info from the reader\u0027s/writer\u0027s netns vs only\n  from the opener\u0027s netns.\n\n- current-\u003ensproxy can be NULL in some cases, resulting in an \u0027Oops\u0027\n  (null-ptr-deref), e.g. when the current task is exiting, as spotted by\n  syzbot [1] using acct(2).\n\nThe \u0027pernet\u0027 structure can be obtained from the table-\u003edata using\ncontainer_of()."
    },
    {
      "lang": "es",
      "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: mptcp: sysctl: blackhole timeout: avoid using current-\u0026gt;nsproxy Como se mencion\u00f3 en el commit anterior, no se recomienda usar la estructura \u0027net\u0027 a trav\u00e9s de \u0027current\u0027 por diferentes razones: - Inconsistencia: obtener informaci\u00f3n de las redes de red del lector/escritor frente a solo de las redes de red del abridor. - current-\u0026gt;nsproxy puede ser NULL en algunos casos, lo que resulta en un \u0027Oops\u0027 (null-ptr-deref), por ejemplo, cuando la tarea actual est\u00e1 saliendo, como lo detect\u00f3 syzbot [1] usando acct(2). La estructura \u0027pernet\u0027 se puede obtener de table-\u0026gt;data usando Container_of()."
    }
  ],
  "id": "CVE-2025-21641",
  "lastModified": "2025-01-19T11:15:09.643",
  "metrics": {},
  "published": "2025-01-19T11:15:09.643",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/4c74fbdc5ab95b13945be01e6065940b68222db7"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/92cf7a51bdae24a32c592adcdd59a773ae149289"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Awaiting Analysis"
}


Log in or create an account to share your comment.




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.