smb: client: delete compound mids on send failure before unlock
In the Linux kernel, the following vulnerability has been resolved: smb: client: delete compound mids on send failure before unlock When sending a compound request fails, smb_send_rqst() kicks off a reconnect. compound_send_recv() still has those mids on pending_mid_q, but it unlocks the server without removing them first. During reconnect, cifs_abort_connection() walks pending_mid_q and runs each mid callback. With no response yet, those callbacks return credits and drop in_flight. Then compound_send_recv()'s send-error path returns the same credits again. in_flight ends up decremented twice and smb2_add_credits() WARNs. syzbot hits this during SMB2_negotiate when the socket send fails. cifs_call_async() already calls delete_mid() before unlock on send failure. Do the same for compound chains and set cancelled_mid[] so the out: path does not delete them again.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 7.2.9
- CVEs
- CVE-2026-98449
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 21:29 UTC · Revision 1
Source evidence
smb: client: delete compound mids on send failure before unlock
core-osv · Original sourcePublished 18 Oct 2026, 15:14 UTC
In the Linux kernel, the following vulnerability has been resolved: smb: client: delete compound mids on send failure before unlock When sending a compound request fails, smb_send_rqst() kicks off a reconnect. compound_send_recv() still has those mids on pending_mid_q, but it unlocks the server without removing them first. During reconnect, cifs_abort_connection() walks pending_mid_q and runs each mid callback. With no response yet, those callbacks return credits and drop in_flight. Then compound_send_recv()'s send-error path returns the same credits again. in_flight ends up decremented twice and smb2_add_credits() WARNs. syzbot hits this during SMB2_negotiate when the socket send fails. cifs_call_async() already calls delete_mid() before unlock on send failure. Do the same for compound chains and set cancelled_mid[] so the out: path does not delete them again.
osv:CVE-2026-98449
Kernel
Fixed versions: 7.2.9
Complete source record
{
"id": "23d5c8da139021e5dd93a461172b036f50a601869baecbe05ec2740ceb33d0b0",
"url": "https://osv.dev/vulnerability/CVE-2026-98449",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "smb: client: delete compound mids on send failure before unlock",
"summary": "In the Linux kernel, the following vulnerability has been resolved: smb: client: delete compound mids on send failure before unlock When sending a compound request fails, smb_send_rqst() kicks off a reconnect. compound_send_recv() still has those mids on pending_mid_q, but it unlocks the server without removing them first. During reconnect, cifs_abort_connection() walks pending_mid_q and runs each mid callback. With no response yet, those callbacks return credits and drop in_flight. Then compound_send_recv()'s send-error path returns the same credits again. in_flight ends up decremented twice and smb2_add_credits() WARNs. syzbot hits this during SMB2_negotiate when the socket send fails. cifs_call_async() already calls delete_mid() before unlock on send failure. Do the same for compound chains and set cancelled_mid[] so the out: path does not delete them again.",
"evidence": "osv:CVE-2026-98449",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "7.2.9",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-98449",
"aliases": [
"CVE-2026-98449"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "ee258d79159afed52ca9372aeb9c1a51e89b32ee"
},
{
"fixed": "70783946f3b5d0c06ec7df0f5e7bec2bfad24efb"
},
{
"fixed": "8f6f8a48399f82f4a83f7b9f25b9707e0062a4f9"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "4.20.11"
},
{
"fixed": "4.21"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "3c57a0be487088b08d9c88998f911eb4a7ba36e4"
}
]
}
],
"versions": [
"v4.20.17",
"v4.20.16",
"v4.20.15",
"v4.20.14",
"v4.20.13",
"v4.20.12",
"v4.20.11"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98449.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "7.2.9"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98449.json"
}
}
],
"modified": "2026-10-28T02:30:39.650518931Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/70783946f3b5d0c06ec7df0f5e7bec2bfad24efb",
"https://git.kernel.org/stable/c/8f6f8a48399f82f4a83f7b9f25b9707e0062a4f9",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98449.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-98449",
"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/2026/98xxx/CVE-2026-98449.json"
}
},
"related_cves": [
{
"value": "CVE-2026-98449",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 507263,
"published_at": "2026-10-18T15:14:59.772+00:00"
}