cve-2025-21636
Vulnerability from cvelistv5
Published
2025-01-19 10:17
Modified
2025-01-23 17:01
Severity ?
EPSS score ?
0.03%
(0.05535)
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.
References
Impacted products
Vendor | Product | Version | |||||||
---|---|---|---|---|---|---|---|---|---|
▼ | Linux | Linux |
Version: d1e462a7a5f359cbb9a0e8fbfafcfb6657034105 Version: d1e462a7a5f359cbb9a0e8fbfafcfb6657034105 Version: d1e462a7a5f359cbb9a0e8fbfafcfb6657034105 Version: d1e462a7a5f359cbb9a0e8fbfafcfb6657034105 Version: d1e462a7a5f359cbb9a0e8fbfafcfb6657034105 |
||||||
|
{ 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->nsproxy\n\nAs mentioned in a previous commit of this series, using the 'net'\nstructure via 'current' is not recommended for different reasons:\n\n- Inconsistency: getting info from the reader's/writer's netns vs only\n from the opener's netns.\n\n- current->nsproxy can be NULL in some cases, resulting in an 'Oops'\n (null-ptr-deref), e.g. when the current task is exiting, as spotted by\n syzbot [1] using acct(2).\n\nThe 'net' structure can be obtained from the table->data using\ncontainer_of().\n\nNote that table->data could also be used directly, as this is the only\nmember needed from the 'net' structure, but that would increase the size\nof this fix, to use '*data' everywhere 'net->sctp.probe_interval' 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->nsproxy", 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-02-27T21:59:09.400\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nsctp: sysctl: plpmtud_probe_interval: avoid using current->nsproxy\\n\\nAs mentioned in a previous commit of this series, using the 'net'\\nstructure via 'current' is not recommended for different reasons:\\n\\n- Inconsistency: getting info from the reader's/writer's netns vs only\\n from the opener's netns.\\n\\n- current->nsproxy can be NULL in some cases, resulting in an 'Oops'\\n (null-ptr-deref), e.g. when the current task is exiting, as spotted by\\n syzbot [1] using acct(2).\\n\\nThe 'net' structure can be obtained from the table->data using\\ncontainer_of().\\n\\nNote that table->data could also be used directly, as this is the only\\nmember needed from the 'net' structure, but that would increase the size\\nof this fix, to use '*data' everywhere 'net->sctp.probe_interval' is\\nused.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: sctp: sysctl: plpmtud_probe_interval: evitar usar current->nsproxy Como se mencionó en un commit anterior de esta serie, no se recomienda usar la estructura 'net' a través de 'current' por diferentes razones: - Inconsistencia: obtener información de los netns del lector/escritor vs solo de los netns del abridor. - current->nsproxy puede ser NULL en algunos casos, lo que resulta en un 'Oops' (null-ptr-deref), por ejemplo cuando la tarea actual está saliendo, como lo detectó syzbot [1] usando acct(2). La estructura 'net' se puede obtener de table->data usando Container_of(). Tenga en cuenta que table->data también se puede usar directamente, ya que este es el único miembro necesario de la estructura 'net', pero eso aumentaría el tamaño de esta corrección, para usar '*data' en todos los lugares donde se use 'net->sctp.probe_interval'.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-476\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.14\",\"versionEndExcluding\":\"5.15.177\",\"matchCriteriaId\":\"7CBBBE2E-F662-4C7C-8FA4-208609AA2652\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.16\",\"versionEndExcluding\":\"6.1.125\",\"matchCriteriaId\":\"9AFD566B-ECC6-46F1-92F7-12A615D5685F\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.2\",\"versionEndExcluding\":\"6.6.72\",\"matchCriteriaId\":\"33E12097-C88A-45B4-9677-2A961A08DD3E\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.7\",\"versionEndExcluding\":\"6.12.10\",\"matchCriteriaId\":\"02D604F6-10D1-4F7B-A022-0888406A1121\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.13:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"62567B3C-6CEE-46D0-BC2E-B3717FBF7D13\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.13:rc2:*:*:*:*:*:*\",\"matchCriteriaId\":\"5A073481-106D-4B15-B4C7-FB0213B8E1D4\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.13:rc3:*:*:*:*:*:*\",\"matchCriteriaId\":\"DE491969-75AE-4A6B-9A58-8FC5AF98798F\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.13:rc4:*:*:*:*:*:*\",\"matchCriteriaId\":\"93C0660D-7FB8-4FBA-892A-B064BA71E49E\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.13:rc5:*:*:*:*:*:*\",\"matchCriteriaId\":\"034C36A6-C481-41F3-AE9A-D116E5BE6895\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.13:rc6:*:*:*:*:*:*\",\"matchCriteriaId\":\"8AF9DC49-2085-4FFB-A7E3-73DFAFECC7F2\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/1dc5da6c4178f3e4b95c631418f72de9f86c0449\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/284a221f8fa503628432c7bb5108277c688c6ffa\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/44ee8635922b6eb940faddb961a8347c6857d722\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/6259d2484d0ceff42245d1f09cc8cb6ee72d847a\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/bcf8c60074e81ed2ac2d35130917175a3949c917\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}", }, }
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.
Title of the comment
Description of the comment
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.