fkie_cve-2022-48977
Vulnerability from fkie_nvd
Published
2024-10-21 20:15
Modified
2024-10-25 18:47
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
can: af_can: fix NULL pointer dereference in can_rcv_filter
Analogue to commit 8aa59e355949 ("can: af_can: fix NULL pointer
dereference in can_rx_register()") we need to check for a missing
initialization of ml_priv in the receive path of CAN frames.
Since commit 4e096a18867a ("net: introduce CAN specific pointer in the
struct net_device") the check for dev->type to be ARPHRD_CAN is not
sufficient anymore since bonding or tun netdevices claim to be CAN
devices but do not initialize ml_priv accordingly.
References
Impacted products
Vendor | Product | Version | |
---|---|---|---|
linux | linux_kernel | * | |
linux | linux_kernel | * | |
linux | linux_kernel | * | |
linux | linux_kernel | * | |
linux | linux_kernel | 6.1 | |
linux | linux_kernel | 6.1 | |
linux | linux_kernel | 6.1 | |
linux | linux_kernel | 6.1 | |
linux | linux_kernel | 6.1 | |
linux | linux_kernel | 6.1 | |
linux | linux_kernel | 6.1 | |
linux | linux_kernel | 6.1 |
{ configurations: [ { nodes: [ { cpeMatch: [ { criteria: "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", matchCriteriaId: "F5FB1A61-365F-4CA9-9623-69C6889A6E49", versionEndExcluding: "5.4.227", versionStartIncluding: "5.4.110", vulnerable: true, }, { criteria: "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", matchCriteriaId: "B4EFBE85-872C-4731-AD53-6DB3F3132B63", versionEndExcluding: "5.10.159", versionStartIncluding: "5.10.28", vulnerable: true, }, { criteria: "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", matchCriteriaId: "34D9B7A6-0CC8-4839-B206-AF0CEAC1CAFE", versionEndExcluding: "5.15.83", versionStartIncluding: "5.11.12", vulnerable: true, }, { criteria: "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", matchCriteriaId: "389392A7-81C4-4C26-884B-8C7CF0F53DA4", versionEndExcluding: "6.0.13", versionStartIncluding: "5.16", vulnerable: true, }, { criteria: "cpe:2.3:o:linux:linux_kernel:6.1:rc1:*:*:*:*:*:*", matchCriteriaId: "E7E331DA-1FB0-4DEC-91AC-7DA69D461C11", vulnerable: true, }, { criteria: "cpe:2.3:o:linux:linux_kernel:6.1:rc2:*:*:*:*:*:*", matchCriteriaId: "17F0B248-42CF-4AE6-A469-BB1BAE7F4705", vulnerable: true, }, { criteria: "cpe:2.3:o:linux:linux_kernel:6.1:rc3:*:*:*:*:*:*", matchCriteriaId: "E2422816-0C14-4B5E-A1E6-A9D776E5C49B", vulnerable: true, }, { criteria: "cpe:2.3:o:linux:linux_kernel:6.1:rc4:*:*:*:*:*:*", matchCriteriaId: "1C6E00FE-5FB9-4D20-A1A1-5A32128F9B76", vulnerable: true, }, { criteria: "cpe:2.3:o:linux:linux_kernel:6.1:rc5:*:*:*:*:*:*", matchCriteriaId: "35B26BE4-43A6-4A36-A7F6-5B3F572D9186", vulnerable: true, }, { criteria: "cpe:2.3:o:linux:linux_kernel:6.1:rc6:*:*:*:*:*:*", matchCriteriaId: "3FFFB0B3-930D-408A-91E2-BAE0C2715D80", vulnerable: true, }, { criteria: "cpe:2.3:o:linux:linux_kernel:6.1:rc7:*:*:*:*:*:*", matchCriteriaId: "8535320E-A0DB-4277-800E-D0CE5BBA59E8", vulnerable: true, }, { criteria: "cpe:2.3:o:linux:linux_kernel:6.1:rc8:*:*:*:*:*:*", matchCriteriaId: "21718AA4-4056-40F2-968E-BDAA465A7872", vulnerable: true, }, ], negate: false, operator: "OR", }, ], }, ], cveTags: [], descriptions: [ { lang: "en", value: "In the Linux kernel, the following vulnerability has been resolved:\n\ncan: af_can: fix NULL pointer dereference in can_rcv_filter\n\nAnalogue to commit 8aa59e355949 (\"can: af_can: fix NULL pointer\ndereference in can_rx_register()\") we need to check for a missing\ninitialization of ml_priv in the receive path of CAN frames.\n\nSince commit 4e096a18867a (\"net: introduce CAN specific pointer in the\nstruct net_device\") the check for dev->type to be ARPHRD_CAN is not\nsufficient anymore since bonding or tun netdevices claim to be CAN\ndevices but do not initialize ml_priv accordingly.", }, { lang: "es", value: "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: can: af_can: fix NULL pointer dereference in can_rcv_filter De manera análoga a el commit 8aa59e355949 (\"can: af_can: fix NULL pointer dereference in can_rx_register()\"), debemos comprobar si falta una inicialización de ml_priv en la ruta de recepción de los marcos CAN. Desde el commit 4e096a18867a (\"net: introduzca el puntero específico de CAN en la estructura net_device\"), la verificación de que dev->type sea ARPHRD_CAN ya no es suficiente ya que los dispositivos de red vinculados o sintonizados afirman ser dispositivos CAN pero no inicializan ml_priv en consecuencia.", }, ], id: "CVE-2022-48977", lastModified: "2024-10-25T18:47:07.357", metrics: { cvssMetricV31: [ { cvssData: { attackComplexity: "LOW", attackVector: "LOCAL", availabilityImpact: "HIGH", baseScore: 5.5, baseSeverity: "MEDIUM", confidentialityImpact: "NONE", integrityImpact: "NONE", privilegesRequired: "LOW", scope: "UNCHANGED", userInteraction: "NONE", vectorString: "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", version: "3.1", }, exploitabilityScore: 1.8, impactScore: 3.6, source: "nvd@nist.gov", type: "Primary", }, ], }, published: "2024-10-21T20:15:09.763", references: [ { source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67", tags: [ "Patch", ], url: "https://git.kernel.org/stable/c/0acc442309a0a1b01bcdaa135e56e6398a49439c", }, { source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67", tags: [ "Patch", ], url: "https://git.kernel.org/stable/c/3982652957e8d79ac32efcb725450580650a8644", }, { source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67", tags: [ "Patch", ], url: "https://git.kernel.org/stable/c/c142cba37de29f740a3852f01f59876af8ae462a", }, { source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67", tags: [ "Patch", ], url: "https://git.kernel.org/stable/c/c42221efb1159d6a3c89e96685ee38acdce86b6f", }, { source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67", tags: [ "Patch", ], url: "https://git.kernel.org/stable/c/fcc63f2f7ee3038d53216edd0d8291e57c752557", }, ], sourceIdentifier: "416baaa9-dc9f-4396-8d5f-8c081fb06d67", vulnStatus: "Analyzed", weaknesses: [ { description: [ { lang: "en", value: "CWE-476", }, ], source: "nvd@nist.gov", type: "Primary", }, ], }
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.