cve-2025-21637
Vulnerability from cvelistv5
Published
2025-01-19 10:17
Modified
2025-01-23 17:01
Severity ?
EPSS score ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
sctp: sysctl: udp_port: 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, but that would
increase the size of this fix, while 'sctp.ctl_sock' still needs to be
retrieved from 'net' structure.
References
Impacted products
Vendor | Product | Version | |||||||
---|---|---|---|---|---|---|---|---|---|
▼ | Linux | Linux |
Version: 046c052b475e7119b6a30e3483e2888fc606a2f8 Version: 046c052b475e7119b6a30e3483e2888fc606a2f8 Version: 046c052b475e7119b6a30e3483e2888fc606a2f8 Version: 046c052b475e7119b6a30e3483e2888fc606a2f8 Version: 046c052b475e7119b6a30e3483e2888fc606a2f8 |
||||||
|
{ "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": "0a0966312ac3eedd7f5f2a766ed4702df39a9a65", "status": "affected", "version": "046c052b475e7119b6a30e3483e2888fc606a2f8", "versionType": "git" }, { "lessThan": "e919197fb8616331f5dc81e4c3cc3d12769cb725", "status": "affected", "version": "046c052b475e7119b6a30e3483e2888fc606a2f8", "versionType": "git" }, { "lessThan": "55627918febdf9d71107a1e68d1528dc591c9a15", "status": "affected", "version": "046c052b475e7119b6a30e3483e2888fc606a2f8", "versionType": "git" }, { "lessThan": "5b77d73f3be5102720fb685b9e6900e3500e1096", "status": "affected", "version": "046c052b475e7119b6a30e3483e2888fc606a2f8", "versionType": "git" }, { "lessThan": "c10377bbc1972d858eaf0ab366a311b39f8ef1b6", "status": "affected", "version": "046c052b475e7119b6a30e3483e2888fc606a2f8", "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.11" }, { "lessThan": "5.11", "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: udp_port: 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, but that would\nincrease the size of this fix, while \u0027sctp.ctl_sock\u0027 still needs to be\nretrieved from \u0027net\u0027 structure." } ], "providerMetadata": { "dateUpdated": "2025-01-23T17:01:19.967Z", "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux" }, "references": [ { "url": "https://git.kernel.org/stable/c/0a0966312ac3eedd7f5f2a766ed4702df39a9a65" }, { "url": "https://git.kernel.org/stable/c/e919197fb8616331f5dc81e4c3cc3d12769cb725" }, { "url": "https://git.kernel.org/stable/c/55627918febdf9d71107a1e68d1528dc591c9a15" }, { "url": "https://git.kernel.org/stable/c/5b77d73f3be5102720fb685b9e6900e3500e1096" }, { "url": "https://git.kernel.org/stable/c/c10377bbc1972d858eaf0ab366a311b39f8ef1b6" } ], "title": "sctp: sysctl: udp_port: avoid using current-\u003ensproxy", "x_generator": { "engine": "bippy-5f407fcff5a0" } } }, "cveMetadata": { "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "assignerShortName": "Linux", "cveId": "CVE-2025-21637", "datePublished": "2025-01-19T10:17:55.321Z", "dateReserved": "2024-12-29T08:45:45.726Z", "dateUpdated": "2025-01-23T17:01:19.967Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1", "vulnerability-lookup:meta": { "nvd": "{\"cve\":{\"id\":\"CVE-2025-21637\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-01-19T11:15:09.217\",\"lastModified\":\"2025-01-23T17:15:25.090\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nsctp: sysctl: udp_port: 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, but that would\\nincrease the size of this fix, while \u0027sctp.ctl_sock\u0027 still needs to be\\nretrieved from \u0027net\u0027 structure.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: sctp: sysctl: udp_port: 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), p. ej. 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, pero eso aumentar\u00eda el tama\u00f1o de esta correcci\u00f3n, mientras que \u0027sctp.ctl_sock\u0027 a\u00fan necesita ser recuperado de la estructura \u0027net\u0027.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/0a0966312ac3eedd7f5f2a766ed4702df39a9a65\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/55627918febdf9d71107a1e68d1528dc591c9a15\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/5b77d73f3be5102720fb685b9e6900e3500e1096\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/c10377bbc1972d858eaf0ab366a311b39f8ef1b6\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/e919197fb8616331f5dc81e4c3cc3d12769cb725\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}" } }
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.