netfilter: nf_tables: prefer nft_chain_validate
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: prefer nft_chain_validate nft_chain_validate already performs loop detection because a cycle will result in a call stack overflow (ctx->level >= NFT_JUMP_STACK_SIZE). It also follows maps via ->validate callback in nft_lookup, so there appears no reason to iterate the maps again. nf_tables_check_loops() and all its helper functions can be removed. This improves ruleset load time significantly, from 23s down to 12s. This also fixes a crash bug. Old loop detection code can result in unbounded recursion: BUG: TASK stack guard page was hit at .... Oops: stack guard page: 0000 [#1] PREEMPT SMP KASAN CPU: 4 PID: 1539 Comm: nft Not tainted 6.10.0-rc5+ #1 [..] with a suitable ruleset during validation of register stores. I can't see any actual reason to attempt to check for this from nft_validate_register_store(), at this point the transaction is still in progress, so we don't have a full picture of the rule graph. For nf-next it might make sense to either remove it or make this depend on table->validate_state in case we could catch an error earlier (for improved error reporting to userspace).
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 4.19.320, 5.10.224, 5.15.165, 5.4.282, 6.1.105, 6.6.46, 6.9.10
- CVEs
- CVE-2024-41042
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 01:01 UTC · Revision 1
Source evidence
netfilter: nf_tables: prefer nft_chain_validate
core-osv · Original sourcePublished 29 Jul 2024, 14:31 UTC
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: prefer nft_chain_validate nft_chain_validate already performs loop detection because a cycle will result in a call stack overflow (ctx->level >= NFT_JUMP_STACK_SIZE). It also follows maps via ->validate callback in nft_lookup, so there appears no reason to iterate the maps again. nf_tables_check_loops() and all its helper functions can be removed. This improves ruleset load time significantly, from 23s down to 12s. This also fixes a crash bug. Old loop detection code can result in unbounded recursion: BUG: TASK stack guard page was hit at .... Oops: stack guard page: 0000 [#1] PREEMPT SMP KASAN CPU: 4 PID: 1539 Comm: nft Not tainted 6.10.0-rc5+ #1 [..] with a suitable ruleset during validation of register stores. I can't see any actual reason to attempt to check for this from nft_validate_register_store(), at this point the transaction is still in progress, so we don't have a full picture of the rule graph. For nf-next it might make sense to either remove it or make this depend on table->validate_state in case we could catch an error earlier (for improved error reporting to userspace).
osv:CVE-2024-41042
Kernel
Fixed versions: 4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.105, 6.6.46, 6.9.10
Complete source record
{
"id": "9acc677cd886741249919c784556d99fc73b4c01c23d253d653bca5ef89685be",
"url": "https://osv.dev/vulnerability/CVE-2024-41042",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "netfilter: nf_tables: prefer nft_chain_validate",
"summary": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: prefer nft_chain_validate nft_chain_validate already performs loop detection because a cycle will result in a call stack overflow (ctx->level >= NFT_JUMP_STACK_SIZE). It also follows maps via ->validate callback in nft_lookup, so there appears no reason to iterate the maps again. nf_tables_check_loops() and all its helper functions can be removed. This improves ruleset load time significantly, from 23s down to 12s. This also fixes a crash bug. Old loop detection code can result in unbounded recursion: BUG: TASK stack guard page was hit at .... Oops: stack guard page: 0000 [#1] PREEMPT SMP KASAN CPU: 4 PID: 1539 Comm: nft Not tainted 6.10.0-rc5+ #1 [..] with a suitable ruleset during validation of register stores. I can't see any actual reason to attempt to check for this from nft_validate_register_store(), at this point the transaction is still in progress, so we don't have a full picture of the rule graph. For nf-next it might make sense to either remove it or make this depend on table->validate_state in case we could catch an error earlier (for improved error reporting to userspace).",
"evidence": "osv:CVE-2024-41042",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.19.320",
"evidence": "/affected/1/ranges"
},
{
"value": "5.4.282",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.224",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.165",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.105",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.46",
"evidence": "/affected/1/ranges"
},
{
"value": "6.9.10",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2024-41042",
"aliases": [
"CVE-2024-41042"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "20a69341f2d00cd042e81c82289fba8a13c05a25"
},
{
"fixed": "1947e4c3346faa8ac7e343652c0fd3b3e394202f"
},
{
"fixed": "cd4348e0a50286282c314ad6d2b0740e7c812c24"
},
{
"fixed": "31c35f9f89ef585f1edb53e17ac73a0ca4a9712b"
},
{
"fixed": "8246b7466c8da49d0d9e85e26cbd69dd6d3e3d1e"
},
{
"fixed": "b6b6e430470e1c3c5513311cb35a15a205595abe"
},
{
"fixed": "717c91c6ed73e248de6a15bc53adefb81446c9d0"
},
{
"fixed": "9df785aeb7dcc8efd1d4110bb27d26005298ebae"
},
{
"fixed": "cff3bd012a9512ac5ed858d38e6ed65f6391008c"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-41042.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "3.13.0"
},
{
"fixed": "4.19.320"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.282"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.224"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.165"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.105"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.46"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.9.10"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-41042.json"
}
}
],
"modified": "2026-10-28T02:30:48.748309639Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/1947e4c3346faa8ac7e343652c0fd3b3e394202f",
"https://git.kernel.org/stable/c/31c35f9f89ef585f1edb53e17ac73a0ca4a9712b",
"https://git.kernel.org/stable/c/717c91c6ed73e248de6a15bc53adefb81446c9d0",
"https://git.kernel.org/stable/c/8246b7466c8da49d0d9e85e26cbd69dd6d3e3d1e",
"https://git.kernel.org/stable/c/9df785aeb7dcc8efd1d4110bb27d26005298ebae",
"https://git.kernel.org/stable/c/b6b6e430470e1c3c5513311cb35a15a205595abe",
"https://git.kernel.org/stable/c/cd4348e0a50286282c314ad6d2b0740e7c812c24",
"https://git.kernel.org/stable/c/cff3bd012a9512ac5ed858d38e6ed65f6391008c",
"https://lists.debian.org/debian-lts-announce/2024/10/msg00003.html",
"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/41xxx/CVE-2024-41042.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-41042",
"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/2024/41xxx/CVE-2024-41042.json"
}
},
"related_cves": [
{
"value": "CVE-2024-41042",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 516816,
"published_at": "2024-07-29T14:31:55.53+00:00"
}