An issue was discovered in the Linux kernel through 6.1-rc8. brcm_nvram_parse in drivers/nvmem/brcm_nvram.c lacks check of the return value of kzalloc() and will cause the NULL Pointer Dereference. Reference: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b0576ade3aaf24b376ea1a4406ae138e2a22b0c0
Memory allocations with the GFP_KERNEL should not be considered as CVE if alloc small amount of memory (based on " GFP_KERNEL - both background and direct reclaim are allowed and the default page allocator behavior is used. That means that not costly allocation requests are basically no-fail but there is no guarantee of that behavior so failures have to be checked properly by callers (e.g. OOM killer victim is allowed to fail currently). ", and for more info see: https://lwn.net/Articles/627419/ ). However, particular for this CVE I'm not sure if always small amount of memory request, so it is just in case as potential security issue.
Hello Alex, while doing review of the Vulnerability Assessment report of RHEL 8.6 for the purpose of Common Criteria certification, we came across this CVE. Could you update the CVE page https://access.redhat.com/security/cve/CVE-2023-3359 with some publicly facing statement why we consider all RHELs as not affected? Especially given the https://www.kernel.org/doc/html/next/core-api/memory-allocation.html that you quoted in comment 4 says that "... but there is no guarantee of that behavior so failures have to be checked properly by callers". Thank you, Jan
In reply to comment #5: > Hello Alex, > > while doing review of the Vulnerability Assessment report of RHEL 8.6 for > the purpose of Common Criteria certification, we came across this CVE. > > Could you update the CVE page > https://access.redhat.com/security/cve/CVE-2023-3359 with some publicly > facing statement why we consider all RHELs as not affected? Especially given > the > > https://www.kernel.org/doc/html/next/core-api/memory-allocation.html > > that you quoted in comment 4 says that "... but there is no guarantee of > that behavior so failures have to be checked properly by callers". > > Thank you, Jan Added statement (that "CONFIG_NVMEM_BRCM_NVRAM disabled for all versions of the Red Hat Enterprise Linux").
Perfect, thank you.