rxrpc: Fix missing validation of ticket length in non-XDR key preparsing
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix missing validation of ticket length in non-XDR key preparsing In rxrpc_preparse(), there are two paths for parsing key payloads: the XDR path (for large payloads) and the non-XDR path (for payloads <= 28 bytes). While the XDR path (rxrpc_preparse_xdr_rxkad()) correctly validates the ticket length against AFSTOKEN_RK_TIX_MAX, the non-XDR path fails to do so. This allows an unprivileged user to provide a very large ticket length. When this key is later read via rxrpc_read(), the total token size (toksize) calculation results in a value that exceeds AFSTOKEN_LENGTH_MAX, triggering a WARN_ON(). [ 2001.302904] WARNING: CPU: 2 PID: 2108 at net/rxrpc/key.c:778 rxrpc_read+0x109/0x5c0 [rxrpc] Fix this by adding a check in the non-XDR parsing path of rxrpc_preparse() to ensure the ticket length does not exceed AFSTOKEN_RK_TIX_MAX, bringing it into parity with the XDR parsing logic.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.258, 5.15.209, 6.1.175, 6.12.84, 6.18.25, 6.6.136, 7.0.2
- CVEs
- CVE-2026-31696
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 8 Nov 2026, 02:54 UTC · Revision 1
Source evidence
rxrpc: Fix missing validation of ticket length in non-XDR key preparsing
core-osv · Original sourcePublished 1 May 2026, 13:55 UTC
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix missing validation of ticket length in non-XDR key preparsing In rxrpc_preparse(), there are two paths for parsing key payloads: the XDR path (for large payloads) and the non-XDR path (for payloads <= 28 bytes). While the XDR path (rxrpc_preparse_xdr_rxkad()) correctly validates the ticket length against AFSTOKEN_RK_TIX_MAX, the non-XDR path fails to do so. This allows an unprivileged user to provide a very large ticket length. When this key is later read via rxrpc_read(), the total token size (toksize) calculation results in a value that exceeds AFSTOKEN_LENGTH_MAX, triggering a WARN_ON(). [ 2001.302904] WARNING: CPU: 2 PID: 2108 at net/rxrpc/key.c:778 rxrpc_read+0x109/0x5c0 [rxrpc] Fix this by adding a check in the non-XDR parsing path of rxrpc_preparse() to ensure the ticket length does not exceed AFSTOKEN_RK_TIX_MAX, bringing it into parity with the XDR parsing logic.
osv:CVE-2026-31696
Kernel
Fixed versions: 5.10.258, 5.15.209, 6.1.175, 6.6.136, 6.12.84, 6.18.25, 7.0.2
Complete source record
{
"id": "a0a5559b168054841b54b5ec5fd855cc8f844853a5c597a28fca0f96bd90a9b4",
"url": "https://osv.dev/vulnerability/CVE-2026-31696",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "rxrpc: Fix missing validation of ticket length in non-XDR key preparsing",
"summary": "In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix missing validation of ticket length in non-XDR key preparsing In rxrpc_preparse(), there are two paths for parsing key payloads: the XDR path (for large payloads) and the non-XDR path (for payloads <= 28 bytes). While the XDR path (rxrpc_preparse_xdr_rxkad()) correctly validates the ticket length against AFSTOKEN_RK_TIX_MAX, the non-XDR path fails to do so. This allows an unprivileged user to provide a very large ticket length. When this key is later read via rxrpc_read(), the total token size (toksize) calculation results in a value that exceeds AFSTOKEN_LENGTH_MAX, triggering a WARN_ON(). [ 2001.302904] WARNING: CPU: 2 PID: 2108 at net/rxrpc/key.c:778 rxrpc_read+0x109/0x5c0 [rxrpc] Fix this by adding a check in the non-XDR parsing path of rxrpc_preparse() to ensure the ticket length does not exceed AFSTOKEN_RK_TIX_MAX, bringing it into parity with the XDR parsing logic.",
"evidence": "osv:CVE-2026-31696",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.258",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.209",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.175",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.136",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.84",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.25",
"evidence": "/affected/1/ranges"
},
{
"value": "7.0.2",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-31696",
"aliases": [
"CVE-2026-31696"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "8a7a3eb4ddbe7c7e639170a64adede7cbd5a9247"
},
{
"fixed": "44714dfda386884919ba366411880b6fb3c3efd3"
},
{
"fixed": "41a117dd80371343babc52198d1114e83eb37627"
},
{
"fixed": "9a397aa9b5e53ca63d4d6aefb542832eca389618"
},
{
"fixed": "1fa36cf495b0023e8475d038535c05e4063211e1"
},
{
"fixed": "4458757c020592a3094366e0fb20457383b42f92"
},
{
"fixed": "ce383ba615339f8eaec646a166d2c2b015bb5ca0"
},
{
"fixed": "a1be1c9ece26cea69654f28b255ff9a7906b897b"
},
{
"fixed": "ac33733b10b484d666f97688561670afd5861383"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-31696.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "3.17.0"
},
{
"fixed": "5.10.258"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.209"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.175"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.136"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.84"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.25"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.0.2"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-31696.json"
}
}
],
"modified": "2026-10-28T02:30:53.239237049Z",
"provider": "osv",
"references": [
"https://cert-portal.siemens.com/productcert/html/ssa-784472.html",
"https://git.kernel.org/stable/c/1fa36cf495b0023e8475d038535c05e4063211e1",
"https://git.kernel.org/stable/c/41a117dd80371343babc52198d1114e83eb37627",
"https://git.kernel.org/stable/c/4458757c020592a3094366e0fb20457383b42f92",
"https://git.kernel.org/stable/c/44714dfda386884919ba366411880b6fb3c3efd3",
"https://git.kernel.org/stable/c/9a397aa9b5e53ca63d4d6aefb542832eca389618",
"https://git.kernel.org/stable/c/a1be1c9ece26cea69654f28b255ff9a7906b897b",
"https://git.kernel.org/stable/c/ac33733b10b484d666f97688561670afd5861383",
"https://git.kernel.org/stable/c/ce383ba615339f8eaec646a166d2c2b015bb5ca0",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/31xxx/CVE-2026-31696.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-31696",
"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/31xxx/CVE-2026-31696.json"
}
},
"related_cves": [
{
"value": "CVE-2026-31696",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 521985,
"published_at": "2026-05-01T13:55:57.485+00:00"
}