3 SOC Challenges You Need to Solve Before 2026

2026 will mark a pivotal shift in cybersecurity. Threat actors are moving from experimenting with AI to making it their primary weapon, using it to scale attacks, automate reconnaissance, and craft hyper-realistic social engineering campaigns. The Storm on the Horizon Global world instability,...

CVE-2025-33195: Improper Restriction of Operations within the Bounds of a Memory Buffer

NVIDIA DGX Spark GB10 contains a vulnerability in SROOT firmware, where an attacker could cause unexpected memory buffer operations. A successful exploit of this vulnerability might lead to data tampering, denial of service, or escalation of privileges...

CVE-2025-62497: Cross-Site Request Forgery (CSRF)

Cross-site request forgery vulnerability exists in SNC-CX600W versions prior to Ver.2.8.0. If a user accesses a specially crafted webpage while logged in, unintended operations may be performed...

The Future of Cloud Security: A New Act for Cyber Risk Operations

Qualys, the leader in Cyber Risk Operations, is proud to be recognized in Latio Tech’s 2025 Cloud Security Market Report as a leader in both CTEM and the Cloud Security Ecosystem. This acknowledgement by Latio Tech reinforces the strength of our strategy—anchored by the industry’s first Risk...

EUVD-2025-198576

The security state of the calling processor into Arm® Trusted Firmware TF-A is not used and could potentially allow non-secure processors access to secure memories, access to crypto operations, and the ability to turn on and off subsystems within the SOC...

CVE-2025-48507

The security state of the calling processor into Trusted Firmware TF-A is not used and could potentially allow non-secure processors access to secure memories, access to crypto operations, and the ability to turn on and off subsystems within the SOC...

CVE-2025-48507

The security state of the calling processor into Trusted Firmware TF-A is not used and could potentially allow non-secure processors access to secure memories, access to crypto operations, and the ability to turn on and off subsystems within the SOC...

CVE-2025-48507

The security state of the calling processor into Trusted Firmware TF-A is not used and could potentially allow non-secure processors access to secure memories, access to crypto operations, and the ability to turn on and off subsystems within the SOC...

CVE-2025-48507

The security state of the calling processor into Trusted Firmware TF-A is not used and could potentially allow non-secure processors access to secure memories, access to crypto operations, and the ability to turn on and off subsystems within the SOC...

CVE-2025-48507

CVE-2025-48507 concerns the unused security state of the calling processor in Arm Trusted Firmware (TF-A) , which could allow a non-secure processor to access secure memories , perform privileged cryptographic operations , and control subsystems within the SOC. Documented exposure stems from AMD-...

PT-2025-47853

Name of the Vulnerable Software and Affected Versions Arm® Trusted Firmware TF-A affected versions not specified Description The security state of the calling processor when entering Arm® Trusted Firmware TF-A is not properly utilized. This could allow processors operating in a non-secure state t...

CVE-2025-48507: Improper Validation of Specified Quantity in Input

The security state of the calling processor into Trusted Firmware TF-A is not used and could potentially allow non-secure processors access to secure memories, access to crypto operations, and the ability to turn on and off subsystems within the SOC...

AMD Zynq UltraScale+ 安全漏洞

AMD Zynq UltraScale+ is a multiprocessor system-on-chip from UltraMicroelectronics AMD. A security vulnerability exists in AMD Zynq UltraScale+ that originates from the unused security state of the calling processor and could result in a non-secure processor accessing secure memory or cryptograph...

Revert "NFSD: Remove the cap on number of operations per NFSv4 COMPOUND"

...

Linux Distros Unpatched Vulnerability : CVE-2025-40210

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - Revert NFSD: Remove the cap on number of operations per NFSv4 COMPOUND I've found that pynfs COMP6 now leaves the connection or lease in a strange state, which...

JLSEC-2025-223 An issue was discovered in Mbed TLS 2.x before 2.28.7 and 3.x before 3.5.2

An issue was discovered in Mbed TLS 2.x before 2.28.7 and 3.x before 3.5.2. There was a timing side channel in RSA private operations. This side channel could be sufficient for a local attacker to recover the plaintext. It requires the attacker to send a large number of messages for decryption, a...

JLSEC-2025-232 Side channel in RSA key generation and operations (SSBleed, M-Step)

Vulnerability Mbed TLS's modular inversion routine and GCD routine are vulnerable to local timing attacks in a number of settings discussed below. These functions are used in RSA, making the following operations vulnerable in all configurations: - RSA key generation with any API mbedtlsrsagenkey...

UBUNTU-CVE-2025-40210

In the Linux kernel, the following vulnerability has been resolved: Revert "NFSD: Remove the cap on number of operations per NFSv4 COMPOUND" I've found that pynfs COMP6 now leaves the connection or lease in a strange state, which causes CLOSE9 to hang indefinitely. I've dug into it a little, but ...

CVE-2025-40210

CVE-2025-40210 concerns the Linux kernel NFSD: NFSv4 COMPOUND operation cap. Public advisories describe that the change removing the cap on operations per COMPOUND can lead to a problematic state in pynfs COMP6 and a potential vulnerability if an attacker specifies an arbitrarily large op count i...

CVE-2025-40210 Revert "NFSD: Remove the cap on number of operations per NFSv4 COMPOUND"

In the Linux kernel, the following vulnerability has been resolved: Revert "NFSD: Remove the cap on number of operations per NFSv4 COMPOUND" I've found that pynfs COMP6 now leaves the connection or lease in a strange state, which causes CLOSE9 to hang indefinitely. I've dug into it a little, but ...