OESA-2025-2313 (CVE-2025-38693)
Vulnerability from osv_openeuler – Published: 2025-09-19 11:09 – Updated: 2026-08-06 11:09 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved:
media: dvb-frontends: w7090p: fix null-ptr-deref in w7090p_tuner_write_serpar and w7090p_tuner_read_serpar
In w7090p_tuner_write_serpar, msg is controlled by user. When msg[0].buf is null and msg[0].len is zero, former checks on msg[0].buf would be passed. If accessing msg[0].buf[2] without sanity check, null pointer deref would happen. We add check on msg[0].len to prevent crash.
Similar commit: commit 0ed554fd769a ("media: dvb-usb: az6027: fix null-ptr-deref in az6027_i2c_xfer()")(CVE-2025-38693)
In the Linux kernel, the following vulnerability has been resolved:
gfs2: Validate i_depth for exhash directories
A fuzzer test introduced corruption that ends up with a depth of 0 in dir_e_read(), causing an undefined shift by 32 at:
index = hash >> (32 - dip->i_depth);
As calculated in an open-coded way in dir_make_exhash(), the minimum depth for an exhash directory is ilog2(sdp->sd_hash_ptrs) and 0 is invalid as sdp->sd_hash_ptrs is fixed as sdp->bsize / 16 at mount time.
So we can avoid the undefined behaviour by checking for depth values lower than the minimum in gfs2_dinode_in(). Values greater than the maximum are already being checked for there.
Also switch the calculation in dir_make_exhash() to use ilog2() to clarify how the depth is calculated.
Tested with the syzkaller repro.c and xfstests '-g quick'.(CVE-2025-38710)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"kernel-5.10.0-282.0.0.184.oe2203sp3.aarch64.rpm",
"kernel-debuginfo-5.10.0-282.0.0.184.oe2203sp3.aarch64.rpm",
"kernel-debugsource-5.10.0-282.0.0.184.oe2203sp3.aarch64.rpm",
"kernel-devel-5.10.0-282.0.0.184.oe2203sp3.aarch64.rpm",
"kernel-headers-5.10.0-282.0.0.184.oe2203sp3.aarch64.rpm",
"kernel-source-5.10.0-282.0.0.184.oe2203sp3.aarch64.rpm",
"kernel-tools-5.10.0-282.0.0.184.oe2203sp3.aarch64.rpm",
"kernel-tools-debuginfo-5.10.0-282.0.0.184.oe2203sp3.aarch64.rpm",
"kernel-tools-devel-5.10.0-282.0.0.184.oe2203sp3.aarch64.rpm",
"perf-5.10.0-282.0.0.184.oe2203sp3.aarch64.rpm",
"perf-debuginfo-5.10.0-282.0.0.184.oe2203sp3.aarch64.rpm",
"python3-perf-5.10.0-282.0.0.184.oe2203sp3.aarch64.rpm",
"python3-perf-debuginfo-5.10.0-282.0.0.184.oe2203sp3.aarch64.rpm"
],
"src": [
"kernel-5.10.0-282.0.0.184.oe2203sp3.src.rpm"
],
"x86_64": [
"kernel-5.10.0-282.0.0.184.oe2203sp3.x86_64.rpm",
"kernel-debuginfo-5.10.0-282.0.0.184.oe2203sp3.x86_64.rpm",
"kernel-debugsource-5.10.0-282.0.0.184.oe2203sp3.x86_64.rpm",
"kernel-devel-5.10.0-282.0.0.184.oe2203sp3.x86_64.rpm",
"kernel-headers-5.10.0-282.0.0.184.oe2203sp3.x86_64.rpm",
"kernel-source-5.10.0-282.0.0.184.oe2203sp3.x86_64.rpm",
"kernel-tools-5.10.0-282.0.0.184.oe2203sp3.x86_64.rpm",
"kernel-tools-debuginfo-5.10.0-282.0.0.184.oe2203sp3.x86_64.rpm",
"kernel-tools-devel-5.10.0-282.0.0.184.oe2203sp3.x86_64.rpm",
"perf-5.10.0-282.0.0.184.oe2203sp3.x86_64.rpm",
"perf-debuginfo-5.10.0-282.0.0.184.oe2203sp3.x86_64.rpm",
"python3-perf-5.10.0-282.0.0.184.oe2203sp3.x86_64.rpm",
"python3-perf-debuginfo-5.10.0-282.0.0.184.oe2203sp3.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP3",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-22.03-LTS-SP3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.10.0-282.0.0.184.oe2203sp3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: dvb-frontends: w7090p: fix null-ptr-deref in w7090p_tuner_write_serpar and w7090p_tuner_read_serpar\n\nIn w7090p_tuner_write_serpar, msg is controlled by user. When msg[0].buf is null and msg[0].len is zero, former checks on msg[0].buf would be passed. If accessing msg[0].buf[2] without sanity check, null pointer deref would happen. We add\ncheck on msg[0].len to prevent crash.\n\nSimilar commit: commit 0ed554fd769a (\u0026quot;media: dvb-usb: az6027: fix null-ptr-deref in az6027_i2c_xfer()\u0026quot;)(CVE-2025-38693)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Validate i_depth for exhash directories\n\nA fuzzer test introduced corruption that ends up with a depth of 0 in\ndir_e_read(), causing an undefined shift by 32 at:\n\n index = hash \u0026gt;\u0026gt; (32 - dip-\u0026gt;i_depth);\n\nAs calculated in an open-coded way in dir_make_exhash(), the minimum\ndepth for an exhash directory is ilog2(sdp-\u0026gt;sd_hash_ptrs) and 0 is\ninvalid as sdp-\u0026gt;sd_hash_ptrs is fixed as sdp-\u0026gt;bsize / 16 at mount time.\n\nSo we can avoid the undefined behaviour by checking for depth values\nlower than the minimum in gfs2_dinode_in(). Values greater than the\nmaximum are already being checked for there.\n\nAlso switch the calculation in dir_make_exhash() to use ilog2() to\nclarify how the depth is calculated.\n\nTested with the syzkaller repro.c and xfstests \u0026apos;-g quick\u0026apos;.(CVE-2025-38710)",
"id": "OESA-2025-2313",
"modified": "2026-08-06T11:09:23Z",
"published": "2025-09-19T11:09:23Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2313"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38693"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38710"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "kernel security update",
"upstream": [
"CVE-2025-38693",
"CVE-2025-38710"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.