{"id":"CVE-2019-14122","url":"https://www.cyber-defence.io/tools/cve/CVE-2019-14122","generatedAt":"2026-10-28T22:21:51.843Z","title":"Memory failure in SKB if it fails to to add the requested padding to the skb in low memory targets or targets with major memory fragmentation in Snapdragon Auto, Snapdragon Mobile in Saipan, SM8150, SM8250, SXR2130","description":"Memory failure in SKB if it fails to to add the requested padding to the skb in low memory targets or targets with major memory fragmentation in Snapdragon Auto, Snapdragon Mobile in Saipan, SM8150, SM8250, SXR2130","published":"2020-04-16T11:15:15.000Z","lastModified":"2026-06-17T02:17:52.000Z","status":"Modified","sourceIdentifier":"product-security@qualcomm.com","cvss":{"version":"3.1","score":7.8,"severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"},"cwe":["CWE-755"],"affected":["qualcomm/saipan firmware","qualcomm/sm8150 firmware","qualcomm/sm8250 firmware","qualcomm/sxr2130 firmware"],"epss":{"score":0.00202,"percentile":0.10122,"date":"2026-10-27","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"high","text":"High impact if exploited, but EPSS currently rates exploitation as unlikely (0.20%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[],"references":[{"url":"https://www.qualcomm.com/company/product-security/bulletins/april-2020-bulletin","tags":["Patch","Vendor Advisory"],"source":"product-security@qualcomm.com"},{"url":"https://www.qualcomm.com/company/product-security/bulletins/april-2020-bulletin","tags":["Patch","Vendor Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2019-14122","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}