Summary
nftables binding to an already bound chain
Workarounds
It's recommended to upgrade
References
- https://www.sesin.at/2022/09/02/cve-2022-39190-linux-kernel-up-to-5-19-5-nf_tables_api-c-nft_verdict_init-denial-of-service/
- https://nvd.nist.gov/vuln/detail/CVE-2022-39190
For more information
- Email us at [email protected]
Impact
An issue was discovered in net/netfilter/nf_tables_api.c in the Linux kernel. A denial of service can occur upon binding to an already bound chain.
Affected by this vulnerability is the function nft_verdict_init of the file net/netfilter/nf_tables_api.c. The manipulation with an unknown input leads to a denial of service vulnerability. The program does not release or incorrectly releases a resource before it is made available for re-use.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The fix has been backported to 5.15.64 version of the upstream Linux kernel (5.15 is the upstream Kernel long term version Talos ships with). Talos >= v1.2.0 is shipped with Linux Kernel 5.15.64 fixing the above issue.
Frequently Asked Questions
- What is GHSA-JR8J-2JHP-M67V? GHSA-JR8J-2JHP-M67V is a medium-severity security vulnerability in github.com/siderolabs/talos (go), affecting versions < 1.2.0. It is fixed in 1.2.0.
- Which versions of github.com/siderolabs/talos are affected by GHSA-JR8J-2JHP-M67V? github.com/siderolabs/talos (go) versions < 1.2.0 is affected.
- Is there a fix for GHSA-JR8J-2JHP-M67V? Yes. GHSA-JR8J-2JHP-M67V is fixed in 1.2.0. Upgrade to this version or later.
- Is GHSA-JR8J-2JHP-M67V exploitable, and should I be worried? Whether GHSA-JR8J-2JHP-M67V is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-JR8J-2JHP-M67V is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-JR8J-2JHP-M67V? Upgrade
github.com/siderolabs/talosto 1.2.0 or later.