bnxt_en: Fix error handling path in bnxt_init_chip()
In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix error handling path in bnxt_init_chip() WARN_ON() is triggered in __flush_work() if bnxt_init_chip() fails because we call cancel_work_sync() on dim work that has not been initialized. WARNING: CPU: 37 PID: 5223 at kernel/workqueue.c:4201 __flush_work.isra.0+0x212/0x230 The driver relies on the BNXT_STATE_NAPI_DISABLED bit to check if dim work has already been cancelled. But in the bnxt_open() path, BNXT_STATE_NAPI_DISABLED is not set and this causes the error path to think that it needs to cancel the uninitalized dim work. Fix it by setting BNXT_STATE_NAPI_DISABLED during initialization. The bit will be cleared when we enable NAPI and initialize dim work.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.12.28, 6.14.6
- CVEs
- CVE-2025-37895
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 16:15 UTC · Revision 1
Source evidence
bnxt_en: Fix error handling path in bnxt_init_chip()
core-osv · Original sourcePublished 20 May 2025, 15:21 UTC
In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix error handling path in bnxt_init_chip() WARN_ON() is triggered in __flush_work() if bnxt_init_chip() fails because we call cancel_work_sync() on dim work that has not been initialized. WARNING: CPU: 37 PID: 5223 at kernel/workqueue.c:4201 __flush_work.isra.0+0x212/0x230 The driver relies on the BNXT_STATE_NAPI_DISABLED bit to check if dim work has already been cancelled. But in the bnxt_open() path, BNXT_STATE_NAPI_DISABLED is not set and this causes the error path to think that it needs to cancel the uninitalized dim work. Fix it by setting BNXT_STATE_NAPI_DISABLED during initialization. The bit will be cleared when we enable NAPI and initialize dim work.
osv:CVE-2025-37895
Kernel
Fixed versions: 6.12.28, 6.14.6
Complete source record
{
"id": "1d01c40f1a3b0f3225e80120591ad540034e2f1b0b38811132e1785383939315",
"url": "https://osv.dev/vulnerability/CVE-2025-37895",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "bnxt_en: Fix error handling path in bnxt_init_chip()",
"summary": "In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix error handling path in bnxt_init_chip() WARN_ON() is triggered in __flush_work() if bnxt_init_chip() fails because we call cancel_work_sync() on dim work that has not been initialized. WARNING: CPU: 37 PID: 5223 at kernel/workqueue.c:4201 __flush_work.isra.0+0x212/0x230 The driver relies on the BNXT_STATE_NAPI_DISABLED bit to check if dim work has already been cancelled. But in the bnxt_open() path, BNXT_STATE_NAPI_DISABLED is not set and this causes the error path to think that it needs to cancel the uninitalized dim work. Fix it by setting BNXT_STATE_NAPI_DISABLED during initialization. The bit will be cleared when we enable NAPI and initialize dim work.",
"evidence": "osv:CVE-2025-37895",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.12.28",
"evidence": "/affected/1/ranges"
},
{
"value": "6.14.6",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2025-37895",
"aliases": [
"CVE-2025-37895"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "f697217f980ffc796c72c34dbf7d59a6b1996888"
},
{
"fixed": "e039b00ddbfeaa0dc59b8659be114f1a1b37c5bf"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "40452969a50652e3cbf89dac83d54eebf2206d27"
},
{
"fixed": "21116727f452474502ee74f956d5e7466103e19b"
},
{
"fixed": "9ab7a709c926c16b4433cf02d04fcbcf35aaab2b"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "6.12.10"
},
{
"fixed": "6.12.28"
}
]
}
],
"versions": [
"v6.12.27",
"v6.12.26",
"v6.12.25",
"v6.12.24",
"v6.12.23",
"v6.12.22",
"v6.12.21",
"v6.12.20",
"v6.12.19",
"v6.12.18",
"v6.12.17",
"v6.12.16",
"v6.12.15",
"v6.12.14",
"v6.12.13",
"v6.12.12",
"v6.12.11",
"v6.12.10"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-37895.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "6.12.28"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.14.6"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-37895.json"
}
}
],
"modified": "2026-10-28T02:30:37.402496647Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/21116727f452474502ee74f956d5e7466103e19b",
"https://git.kernel.org/stable/c/9ab7a709c926c16b4433cf02d04fcbcf35aaab2b",
"https://git.kernel.org/stable/c/e039b00ddbfeaa0dc59b8659be114f1a1b37c5bf",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/37xxx/CVE-2025-37895.json",
"https://nvd.nist.gov/vuln/detail/CVE-2025-37895",
"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/37xxx/CVE-2025-37895.json"
}
},
"related_cves": [
{
"value": "CVE-2025-37895",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 504580,
"published_at": "2025-05-20T15:21:32.045+00:00"
}