CVE-2025-21641
Vulnerability from cvelistv5
Published
2025-01-19 10:17
Modified
2025-01-20 06:29
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().
Impacted products
Vendor Product Version
Linux Linux Version: 27069e7cb3d1cea9377069266acf19b9cc5ad0ae
Version: 27069e7cb3d1cea9377069266acf19b9cc5ad0ae
Create a notification for this product.
   Linux Linux Version: 6.12
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/mptcp/ctrl.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "4c74fbdc5ab95b13945be01e6065940b68222db7",
              "status": "affected",
              "version": "27069e7cb3d1cea9377069266acf19b9cc5ad0ae",
              "versionType": "git"
            },
            {
              "lessThan": "92cf7a51bdae24a32c592adcdd59a773ae149289",
              "status": "affected",
              "version": "27069e7cb3d1cea9377069266acf19b9cc5ad0ae",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/mptcp/ctrl.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.12"
            },
            {
              "lessThan": "6.12",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.10",
              "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\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()."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-01-20T06:29:58.708Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/4c74fbdc5ab95b13945be01e6065940b68222db7"
        },
        {
          "url": "https://git.kernel.org/stable/c/92cf7a51bdae24a32c592adcdd59a773ae149289"
        }
      ],
      "title": "mptcp: sysctl: blackhole timeout: avoid using current-\u003ensproxy",
      "x_generator": {
        "engine": "bippy-5f407fcff5a0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-21641",
    "datePublished": "2025-01-19T10:17:58.351Z",
    "dateReserved": "2024-12-29T08:45:45.727Z",
    "dateUpdated": "2025-01-20T06:29:58.708Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-21641\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-01-19T11:15:09.643\",\"lastModified\":\"2025-01-19T11:15:09.643\",\"vulnStatus\":\"Received\",\"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().\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/4c74fbdc5ab95b13945be01e6065940b68222db7\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/92cf7a51bdae24a32c592adcdd59a773ae149289\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




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.