fkie_cve-2024-40996
Vulnerability from fkie_nvd
Published
2024-07-12 13:15
Modified
2024-11-21 09:32
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
bpf: Avoid splat in pskb_pull_reason
syzkaller builds (CONFIG_DEBUG_NET=y) frequently trigger a debug
hint in pskb_may_pull.
We'd like to retain this debug check because it might hint at integer
overflows and other issues (kernel code should pull headers, not huge
value).
In bpf case, this splat isn't interesting at all: such (nonsensical)
bpf programs are typically generated by a fuzzer anyway.
Do what Eric suggested and suppress such warning.
For CONFIG_DEBUG_NET=n we don't need the extra check because
pskb_may_pull will do the right thing: return an error without the
WARN() backtrace.
References
Impacted products
Vendor | Product | Version | |
---|---|---|---|
linux | linux_kernel | * | |
linux | linux_kernel | * | |
linux | linux_kernel | * | |
linux | linux_kernel | 6.10 | |
linux | linux_kernel | 6.10 | |
linux | linux_kernel | 6.10 | |
linux | linux_kernel | 6.10 |
{ configurations: [ { nodes: [ { cpeMatch: [ { criteria: "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", matchCriteriaId: "57BC82B2-9518-4E49-8B35-1E0659D07153", versionEndExcluding: "6.1.96", versionStartIncluding: "6.1.86", vulnerable: true, }, { criteria: "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", matchCriteriaId: "11D787AB-6330-424C-8EDA-145219D31344", versionEndExcluding: "6.6.36", versionStartIncluding: "6.6.27", vulnerable: true, }, { criteria: "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", matchCriteriaId: "1833E4E3-20C1-46FE-BE78-1FA23B2452C0", versionEndExcluding: "6.9.7", versionStartIncluding: "6.9", vulnerable: true, }, { criteria: "cpe:2.3:o:linux:linux_kernel:6.10:rc1:*:*:*:*:*:*", matchCriteriaId: "2EBB4392-5FA6-4DA9-9772-8F9C750109FA", vulnerable: true, }, { criteria: "cpe:2.3:o:linux:linux_kernel:6.10:rc2:*:*:*:*:*:*", matchCriteriaId: "331C2F14-12C7-45D5-893D-8C52EE38EA10", vulnerable: true, }, { criteria: "cpe:2.3:o:linux:linux_kernel:6.10:rc3:*:*:*:*:*:*", matchCriteriaId: "3173713D-909A-4DD3-9DD4-1E171EB057EE", vulnerable: true, }, { criteria: "cpe:2.3:o:linux:linux_kernel:6.10:rc4:*:*:*:*:*:*", matchCriteriaId: "79F18AFA-40F7-43F0-BA30-7BDB65F918B9", vulnerable: true, }, ], negate: false, operator: "OR", }, ], }, ], cveTags: [], descriptions: [ { lang: "en", value: "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Avoid splat in pskb_pull_reason\n\nsyzkaller builds (CONFIG_DEBUG_NET=y) frequently trigger a debug\nhint in pskb_may_pull.\n\nWe'd like to retain this debug check because it might hint at integer\noverflows and other issues (kernel code should pull headers, not huge\nvalue).\n\nIn bpf case, this splat isn't interesting at all: such (nonsensical)\nbpf programs are typically generated by a fuzzer anyway.\n\nDo what Eric suggested and suppress such warning.\n\nFor CONFIG_DEBUG_NET=n we don't need the extra check because\npskb_may_pull will do the right thing: return an error without the\nWARN() backtrace.", }, { lang: "es", value: "En el kernel de Linux, se resolvió la siguiente vulnerabilidad: bpf: evitar splat en pskb_pull_reason compilaciones de syzkaller (CONFIG_DEBUG_NET=y) frecuentemente activa una sugerencia de depuración en pskb_may_pull. Nos gustaría conservar esta verificación de depuración porque podría indicar desbordamientos de enteros y otros problemas (el código del kernel debe extraer encabezados, no valores enormes). En el caso de bpf, este símbolo no es nada interesante: estos programas bpf (sin sentido) normalmente son generados por un fuzzer de todos modos. Haga lo que Eric sugirió y suprima esa advertencia. Para CONFIG_DEBUG_NET=n no necesitamos la verificación adicional porque pskb_may_pull hará lo correcto: devolver un error sin el rastreo WARN().", }, ], id: "CVE-2024-40996", lastModified: "2024-11-21T09:32:01.787", metrics: { cvssMetricV31: [ { cvssData: { attackComplexity: "LOW", attackVector: "LOCAL", availabilityImpact: "HIGH", baseScore: 7.8, baseSeverity: "HIGH", confidentialityImpact: "HIGH", integrityImpact: "HIGH", privilegesRequired: "LOW", scope: "UNCHANGED", userInteraction: "NONE", vectorString: "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", version: "3.1", }, exploitabilityScore: 1.8, impactScore: 5.9, source: "nvd@nist.gov", type: "Primary", }, ], }, published: "2024-07-12T13:15:20.740", references: [ { source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67", tags: [ "Patch", ], url: "https://git.kernel.org/stable/c/2bbe3e5a2f4ef69d13be54f1cf895b4658287080", }, { source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67", tags: [ "Patch", ], url: "https://git.kernel.org/stable/c/5e90258303a358e88737afb5048bee9113beea3a", }, { source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67", tags: [ "Patch", ], url: "https://git.kernel.org/stable/c/7f9644782c559635bd676c12c59389a34ed7c866", }, { source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67", tags: [ "Patch", ], url: "https://git.kernel.org/stable/c/dacc15e9cb248d19e5fc63c54bef0b9b55007761", }, { source: "af854a3a-2127-422b-91ae-364da2661108", tags: [ "Patch", ], url: "https://git.kernel.org/stable/c/2bbe3e5a2f4ef69d13be54f1cf895b4658287080", }, { source: "af854a3a-2127-422b-91ae-364da2661108", tags: [ "Patch", ], url: "https://git.kernel.org/stable/c/5e90258303a358e88737afb5048bee9113beea3a", }, { source: "af854a3a-2127-422b-91ae-364da2661108", tags: [ "Patch", ], url: "https://git.kernel.org/stable/c/7f9644782c559635bd676c12c59389a34ed7c866", }, { source: "af854a3a-2127-422b-91ae-364da2661108", tags: [ "Patch", ], url: "https://git.kernel.org/stable/c/dacc15e9cb248d19e5fc63c54bef0b9b55007761", }, ], sourceIdentifier: "416baaa9-dc9f-4396-8d5f-8c081fb06d67", vulnStatus: "Modified", weaknesses: [ { description: [ { lang: "en", value: "NVD-CWE-noinfo", }, ], 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.