Comparison Overview
MaxLinear

MaxLinear
5966 La Place Ct, Carlsbad, California, 92008, US
Last Update: 10/03/2026
MaxLinear is a fabless semiconductor company that provides systems-on-chip (SoC) solutions used for broadband, mobile and wireline infrastructure, data center, and industrial and multi-market applications. We bring our customers a competitive advantage through enginee...

AMD
2485 Augustine Drive, Santa Clara, 95054, US
Last Update: 16/08/2026
We care deeply about transforming lives with AMD technology to enrich our industry, our communities, and the world. Our mission is to build great products that accelerate next-generation computing experiences – the building blocks for the data center, artificial intelli...
Compliance Ranges Comparison

MaxLinear







AMD






Benchmark & Cyber Underwriting Signals
Incidents vs Semiconductor Manufacturing Industry Avg (This Year)
No incidents recorded for MaxLinear in 2026.
Incidents vs Semiconductor Manufacturing Industry Avg (This Year)
AMD has 94.17% more incidents than the average of all companies with at least one recorded incident.
Incident History - MaxLinear (X = Date, Y = Severity)
MaxLinear cyber incidents detection timeline including parent company and subsidiaries.
Incident History - AMD (X = Date, Y = Severity)
AMD cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

MaxLinear

AMD
FAQ
Latest Global CVEs
A vulnerability was detected in D-Link DIR-825M 1.1.8. This affects the function sub_46725C of the file /boafrm/formDiskFormat of the component Disk Formatting Handler Endpoint. The manipulation of the argument partition results in stack-based buffer overflow. The attack can be executed remotely. The exploit is now public and may be used.
A security vulnerability has been detected in Open Asset Import Library Assimp up to 6.0.2. The impacted element is the function MD5Importer::MakeDataUnique of the file code/AssetLib/MD5/MD5Loader.cpp. The manipulation of the argument iNewIndex leads to heap-based buffer overflow. The attack can only be performed from a local environment. The identifier of the patch is bf9dabb617c46e5133dac65cca6bff177917afcb. Applying a patch is the recommended action to fix this issue.
A weakness has been identified in Open5GS up to 2.7.7. The affected element is the function smf_nudm_sdm_handle_get of the file src/smf/nudm-handler.c of the component SMF. Executing a manipulation of the argument preemptCap can lead to reachable assertion. The attack may be launched remotely. Upgrading to version 2.8.0 is sufficient to fix this issue. This patch is called 4554405f29bffd7562abedbee63484825bd90cd5. You should upgrade the affected component.
- https://github.com/open5gs/open5gs/
- https://github.com/open5gs/open5gs/commit/4554405f29bffd7562abedbee63484825bd90cd5
- https://github.com/open5gs/open5gs/issues/4455
- https://github.com/open5gs/open5gs/releases/tag/v2.8.0
- https://vuldb.com/cve/CVE-2026-82590
- https://vuldb.com/submit/891893
- https://vuldb.com/vuln/397085
- https://vuldb.com/vuln/397085/cti
A security flaw has been discovered in Open5GS up to 2.7.7. Impacted is the function amf_namf_comm_handle_n1_n2_message_transfer of the file src/amf/namf-handler.c of the component N1-N2 Message Handler. Performing a manipulation of the argument N1N2MessageTransferReqData.n2InfoContainer.smInfo.n2InfoContent.ngapIeType results in denial of service. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks. Upgrading to version 2.8.0 is recommended to address this issue. The patch is named abf8a836564b966b5141110fc25ed413c4f17522. It is advisable to upgrade the affected component.
- https://github.com/open5gs/open5gs/
- https://github.com/open5gs/open5gs/commit/abf8a836564b966b5141110fc25ed413c4f17522
- https://github.com/open5gs/open5gs/issues/4396
- https://github.com/open5gs/open5gs/releases/tag/v2.8.0
- https://vuldb.com/cve/CVE-2026-82589
- https://vuldb.com/submit/891892
- https://vuldb.com/vuln/397084
- https://vuldb.com/vuln/397084/cti
A vulnerability was identified in Open5GS up to 2.7.7. This issue affects some unknown processing of the file src/amf/namf-handler.c of the component Transfer Endpoint. Such manipulation leads to null pointer dereference. The attack can be launched remotely. Upgrading to version 2.8.0 is capable of addressing this issue. The name of the patch is abf8a836564b966b5141110fc25ed413c4f17522. Upgrading the affected component is advised.
- https://github.com/open5gs/open5gs/
- https://github.com/open5gs/open5gs/commit/abf8a836564b966b5141110fc25ed413c4f17522
- https://github.com/open5gs/open5gs/issues/4397
- https://github.com/open5gs/open5gs/releases/tag/v2.8.0
- https://vuldb.com/cve/CVE-2026-82588
- https://vuldb.com/submit/891891
- https://vuldb.com/vuln/397083
- https://vuldb.com/vuln/397083/cti