net: hibmcge: fix the division by zero issue
In the Linux kernel, the following vulnerability has been resolved: net: hibmcge: fix the division by zero issue When the network port is down, the queue is released, and ring->len is 0. In debugfs, hbg_get_queue_used_num() will be called, which may lead to a division by zero issue. This patch adds a check, if ring->len is 0, hbg_get_queue_used_num() directly returns 0.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.15.11, 6.16.2
- CVEs
- CVE-2025-38719
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 6 Nov 2026, 00:06 UTC · Revision 1
Source evidence
net: hibmcge: fix the division by zero issue
core-osv · Original sourcePublished 4 Sept 2025, 15:33 UTC
In the Linux kernel, the following vulnerability has been resolved: net: hibmcge: fix the division by zero issue When the network port is down, the queue is released, and ring->len is 0. In debugfs, hbg_get_queue_used_num() will be called, which may lead to a division by zero issue. This patch adds a check, if ring->len is 0, hbg_get_queue_used_num() directly returns 0.
osv:CVE-2025-38719
Kernel
Fixed versions: 6.15.11, 6.16.2
Complete source record
{
"id": "cddb2b123163dc466174f71354c6437235d4b1aae29172b521934eddd378d677",
"url": "https://osv.dev/vulnerability/CVE-2025-38719",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "net: hibmcge: fix the division by zero issue",
"summary": "In the Linux kernel, the following vulnerability has been resolved: net: hibmcge: fix the division by zero issue When the network port is down, the queue is released, and ring->len is 0. In debugfs, hbg_get_queue_used_num() will be called, which may lead to a division by zero issue. This patch adds a check, if ring->len is 0, hbg_get_queue_used_num() directly returns 0.",
"evidence": "osv:CVE-2025-38719",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.15.11",
"evidence": "/affected/1/ranges"
},
{
"value": "6.16.2",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2025-38719",
"aliases": [
"CVE-2025-38719"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "40735e7543f94fc88f58d94fd5f88daa4a2f2c6e"
},
{
"fixed": "c945e1ad4f3b77166a3215dabc0c6c980d4a9c73"
},
{
"fixed": "475e06113c615dafd44262d6d6bd37786f7f4206"
},
{
"fixed": "7004b26f0b64331143eb0b312e77a357a11427ce"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38719.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.15.11"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.16.0"
},
{
"fixed": "6.16.2"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38719.json"
}
}
],
"modified": "2026-10-28T02:30:45.119681276Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/475e06113c615dafd44262d6d6bd37786f7f4206",
"https://git.kernel.org/stable/c/7004b26f0b64331143eb0b312e77a357a11427ce",
"https://git.kernel.org/stable/c/c945e1ad4f3b77166a3215dabc0c6c980d4a9c73",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38719.json",
"https://nvd.nist.gov/vuln/detail/CVE-2025-38719",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38719.json"
}
},
"related_cves": [
{
"value": "CVE-2025-38719",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 513332,
"published_at": "2025-09-04T15:33:13.213+00:00"
}