CVE-2024-1598 is a high severity (CVSS 7.5) potential buffer overflow in unsafe UEFI variable handling in Phoenix SecureCore for Intel Gemini Lake, from 4.1.0.1 before 4.1.0.567. Firmware fixes come through your device maker, so check the Phoenix notice and your vendor's BIOS updates.
What's affected
The record says SecureCore for Intel Gemini Lake is affected from version 4.1.0.1 before 4.1.0.567, with an Intel Celeron N4020 listed among the platform products. Version 4.1.0.567 is the first fixed version by that range.
The Phoenix security notification is the reference, and I could not retrieve its text, so check it for details. Phoenix supplies firmware to device makers, so you usually cannot update it directly. Your laptop, mini PC or embedded board maker decides when a BIOS update ships.
How to check if you're exposed
Find your firmware version from the operating system. On Linux:
sudo dmidecode -s bios-version
sudo dmidecode -s bios-vendor
On Windows, run msinfo32 and read the BIOS Version field. Then compare against your device maker's support page for a BIOS update that mentions this CVE or SecureCore.
To check a whole codebase at once, run the free in-browser dependency scan at gold.safeguard.sh/scan. You can also look up the CVE in the Gold directory, and use reachability analysis to see whether your code calls the affected path.
What to do now
- List devices with Intel Gemini Lake processors and Phoenix firmware.
- Check each maker's support page for a BIOS update that includes the fix.
- Apply the BIOS update using the maker's tool.
- Restrict physical and administrative access to those machines until updated.
- Record firmware versions in your asset inventory.
Why it matters
The record classes this as CWE-121, stack-based buffer overflow. UEFI code read a variable without checking how large it was, so too much data could overwrite memory on the stack.
Firmware bugs matter because firmware runs before the operating system and can persist across reinstalls. The attack usually needs privileged access to write the variable, which keeps the score at 7.5. The record's KEV flag is false. If you cannot update right away, limit who can reach the device with administrative rights, keep operating system updates current, and use the platform's firmware protection settings where the maker provides them. Record the firmware version for each device so that a later update can be tracked and verified.
Quick check
Which versions are fixed?
Anything at or above 4.1.0.567 in this line, per the record.
Can I patch it myself?
Usually not. Firmware updates come from the device maker.
Sources
Last reviewed: 19 October 2026.
