cve-2025-21636
Vulnerability from cvelistv5
Published
2025-01-19 10:17
Modified
2025-01-23 17:01
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: plpmtud_probe_interval: avoid using current->nsproxy As mentioned in a previous commit of this series, 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 'net' structure can be obtained from the table->data using container_of(). Note that table->data could also be used directly, as this is the only member needed from the 'net' structure, but that would increase the size of this fix, to use '*data' everywhere 'net->sctp.probe_interval' is used.
Impacted products
Vendor Product Version
Linux Linux Version: d1e462a7a5f359cbb9a0e8fbfafcfb6657034105
Version: d1e462a7a5f359cbb9a0e8fbfafcfb6657034105
Version: d1e462a7a5f359cbb9a0e8fbfafcfb6657034105
Version: d1e462a7a5f359cbb9a0e8fbfafcfb6657034105
Version: d1e462a7a5f359cbb9a0e8fbfafcfb6657034105
Create a notification for this product.
   Linux Linux Version: 5.14
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/sctp/sysctl.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "1dc5da6c4178f3e4b95c631418f72de9f86c0449",
              "status": "affected",
              "version": "d1e462a7a5f359cbb9a0e8fbfafcfb6657034105",
              "versionType": "git"
            },
            {
              "lessThan": "44ee8635922b6eb940faddb961a8347c6857d722",
              "status": "affected",
              "version": "d1e462a7a5f359cbb9a0e8fbfafcfb6657034105",
              "versionType": "git"
            },
            {
              "lessThan": "284a221f8fa503628432c7bb5108277c688c6ffa",
              "status": "affected",
              "version": "d1e462a7a5f359cbb9a0e8fbfafcfb6657034105",
              "versionType": "git"
            },
            {
              "lessThan": "bcf8c60074e81ed2ac2d35130917175a3949c917",
              "status": "affected",
              "version": "d1e462a7a5f359cbb9a0e8fbfafcfb6657034105",
              "versionType": "git"
            },
            {
              "lessThan": "6259d2484d0ceff42245d1f09cc8cb6ee72d847a",
              "status": "affected",
              "version": "d1e462a7a5f359cbb9a0e8fbfafcfb6657034105",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/sctp/sysctl.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.14"
            },
            {
              "lessThan": "5.14",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.177",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.125",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.72",
              "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\nsctp: sysctl: plpmtud_probe_interval: avoid using current-\u003ensproxy\n\nAs mentioned in a previous commit of this series, using the \u0027net\u0027\nstructure via \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 \u0027net\u0027 structure can be obtained from the table-\u003edata using\ncontainer_of().\n\nNote that table-\u003edata could also be used directly, as this is the only\nmember needed from the \u0027net\u0027 structure, but that would increase the size\nof this fix, to use \u0027*data\u0027 everywhere \u0027net-\u003esctp.probe_interval\u0027 is\nused."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-01-23T17:01:18.814Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/1dc5da6c4178f3e4b95c631418f72de9f86c0449"
        },
        {
          "url": "https://git.kernel.org/stable/c/44ee8635922b6eb940faddb961a8347c6857d722"
        },
        {
          "url": "https://git.kernel.org/stable/c/284a221f8fa503628432c7bb5108277c688c6ffa"
        },
        {
          "url": "https://git.kernel.org/stable/c/bcf8c60074e81ed2ac2d35130917175a3949c917"
        },
        {
          "url": "https://git.kernel.org/stable/c/6259d2484d0ceff42245d1f09cc8cb6ee72d847a"
        }
      ],
      "title": "sctp: sysctl: plpmtud_probe_interval: avoid using current-\u003ensproxy",
      "x_generator": {
        "engine": "bippy-5f407fcff5a0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-21636",
    "datePublished": "2025-01-19T10:17:54.576Z",
    "dateReserved": "2024-12-29T08:45:45.726Z",
    "dateUpdated": "2025-01-23T17:01:18.814Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-21636\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-01-19T11:15:09.110\",\"lastModified\":\"2025-01-23T17:15:24.790\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nsctp: sysctl: plpmtud_probe_interval: avoid using current-\u003ensproxy\\n\\nAs mentioned in a previous commit of this series, using the \u0027net\u0027\\nstructure via \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 \u0027net\u0027 structure can be obtained from the table-\u003edata using\\ncontainer_of().\\n\\nNote that table-\u003edata could also be used directly, as this is the only\\nmember needed from the \u0027net\u0027 structure, but that would increase the size\\nof this fix, to use \u0027*data\u0027 everywhere \u0027net-\u003esctp.probe_interval\u0027 is\\nused.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: sctp: sysctl: plpmtud_probe_interval: evitar usar current-\u0026gt;nsproxy Como se mencion\u00f3 en un commit anterior de esta serie, no se recomienda usar la estructura \u0027net\u0027 a trav\u00e9s de \u0027current\u0027 por diferentes razones: - Inconsistencia: obtener informaci\u00f3n de los netns del lector/escritor vs solo de los netns 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 \u0027net\u0027 se puede obtener de table-\u0026gt;data usando Container_of(). Tenga en cuenta que table-\u0026gt;data tambi\u00e9n se puede usar directamente, ya que este es el \u00fanico miembro necesario de la estructura \u0027net\u0027, pero eso aumentar\u00eda el tama\u00f1o de esta correcci\u00f3n, para usar \u0027*data\u0027 en todos los lugares donde se use \u0027net-\u0026gt;sctp.probe_interval\u0027.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/1dc5da6c4178f3e4b95c631418f72de9f86c0449\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/284a221f8fa503628432c7bb5108277c688c6ffa\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/44ee8635922b6eb940faddb961a8347c6857d722\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/6259d2484d0ceff42245d1f09cc8cb6ee72d847a\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/bcf8c60074e81ed2ac2d35130917175a3949c917\",\"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.