An attacker can trigger a buffer overflow of the Linux kernel, via nft_set_desc_concat_parse(), in order to trigger a denial of service, and possibly to run code. Reference: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/net/netfilter/nf_tables_api.c?id=fecf31ee395b0295f2d7260aa29946b7605f7c85
Is this a duplicate of CVE-2022-1972? Both cves list https://git.kernel.org/linus/fecf31ee395b0295f2d7260aa29946b7605f7c85 as the fix for the issue. Thanks for any clarification you can give.
In reply to comment #9: > Is this a duplicate of CVE-2022-1972? Both cves list > https://git.kernel.org/linus/fecf31ee395b0295f2d7260aa29946b7605f7c85 as the > fix for the issue. > > Thanks for any clarification you can give. Yes. Seems to be a duplicate of CVE-2022-2078, both CVE-2022-1972 and CVE-2022-2078 link to https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/net/netfilter/nf_tables_api.c?id=fecf31ee395b0295f2d7260aa29946b7605f7c85
*** Bug 2092537 has been marked as a duplicate of this bug. ***
(In reply to Alex from comment #10) > In reply to comment #9: > > Is this a duplicate of CVE-2022-1972? Both cves list > > https://git.kernel.org/linus/fecf31ee395b0295f2d7260aa29946b7605f7c85 as the > > fix for the issue. > > > > Thanks for any clarification you can give. > > Yes. Seems to be a duplicate of CVE-2022-2078, > > both CVE-2022-1972 and CVE-2022-2078 > > link to > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/ > net/netfilter/nf_tables_api.c?id=fecf31ee395b0295f2d7260aa29946b7605f7c85 would it make sense to properly reject the CVE-2022-1972 CVE at CNA level. I believe this has potential for some confusion as CVE-2022-1972 was probably assigned earlier, then referenced in https://www.openwall.com/lists/oss-security/2022/06/02/1 but CVE-2022-2078 is the one officially filled https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2078 Regards, Salvatore
OTOH unfortunately CVE-2022-1972 was already used widely as well in advisories (apart the oss-security post), so not sure what is the best outcome.
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2022:6582 https://access.redhat.com/errata/RHSA-2022:6582
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2022:6610 https://access.redhat.com/errata/RHSA-2022:6610
It does, I have requested that CVE-2022-1972 be marked as duplicate of this bug with Mitre.
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2022:7444 https://access.redhat.com/errata/RHSA-2022:7444
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2022:7683 https://access.redhat.com/errata/RHSA-2022:7683
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2022-2078
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.6 Extended Update Support Via RHSA-2024:0724 https://access.redhat.com/errata/RHSA-2024:0724