# SUSE-SU-2026:5096-1: Security update for 2 packages SUSE-SU-2026:5096-1, released November 7, 2026, fixes 81 CVEs across 2 products. None of them is reported as exploited. Patch Radar priority: High. - Web page: https://patchblox.com/security/fix/linux/suse-su-2026-5096-1 - Platform: Linux - Released: Nov 7, 2026 - Priority: High (Closes CVE-2026-47512, high severity) - CVEs: 81, exploited: 0, on CISA KEV: 0 - Vendor advisory: https://osv.dev/vulnerability/SUSE-SU-2026:5096-1 ## Applies to | Product | Release | Fixed in | |---|---|---| | [nvidia-open-driver-G07-signed](https://patchblox.com/security/data/product/linux/nvidia-open-driver-g07-signed.md) | sles 15.6 | 595.112.07-150600.13.31.1 | | [nvidia-open-driver-G07-signed-cuda](https://patchblox.com/security/data/product/linux/nvidia-open-driver-g07-signed-cuda.md) | sles 15.6 | 615.71.09-150600.13.31.1 | ## CVEs this fix closes | CVE | Priority | Title | CVSS | EPSS | Exploitation | |---|---|---|---:|---:|---| | [CVE-2026-47491](https://patchblox.com/security/data/cve/CVE-2026-47491.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47489, , CVE-2026-47492, CVE-2026-47494 | 7.8 | 0.0015 | | | [CVE-2026-47494](https://patchblox.com/security/data/cve/CVE-2026-47494.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47489, CVE-2026-47491, CVE-2026-47492 | 7.8 | 0.0015 | | | [CVE-2026-47501](https://patchblox.com/security/data/cve/CVE-2026-47501.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47500, , CVE-2026-47502, CVE-2026-47504 | 7.8 | 0.0015 | | | [CVE-2026-47504](https://patchblox.com/security/data/cve/CVE-2026-47504.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47500, CVE-2026-47501, CVE-2026-47502 | 7.8 | 0.0015 | | | [CVE-2026-47507](https://patchblox.com/security/data/cve/CVE-2026-47507.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47508, CVE-2026-47509, CVE-2026-47510 | 7.8 | 0.0015 | | | [CVE-2026-47508](https://patchblox.com/security/data/cve/CVE-2026-47508.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47507, , CVE-2026-47509, CVE-2026-47510 | 7.8 | 0.0015 | | | [CVE-2026-47510](https://patchblox.com/security/data/cve/CVE-2026-47510.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47507, CVE-2026-47508, CVE-2026-47509 | 7.8 | 0.0015 | | | [CVE-2026-47511](https://patchblox.com/security/data/cve/CVE-2026-47511.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47512, CVE-2026-47513, CVE-2026-47514 | 7.8 | 0.0015 | | | [CVE-2026-47512](https://patchblox.com/security/data/cve/CVE-2026-47512.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47511, , CVE-2026-47513, CVE-2026-47514 | 7.8 | 0.0015 | | | [CVE-2026-47596](https://patchblox.com/security/data/cve/CVE-2026-47596.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47597, CVE-2026-47598, CVE-2026-47599 | 7.0 | 0.0014 | | | [CVE-2026-47500](https://patchblox.com/security/data/cve/CVE-2026-47500.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47501, CVE-2026-47502, CVE-2026-47504 | 7.8 | 0.0014 | | | [CVE-2026-47513](https://patchblox.com/security/data/cve/CVE-2026-47513.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47511, CVE-2026-47512, , CVE-2026-47514 | 7.8 | 0.0014 | | | [CVE-2026-47514](https://patchblox.com/security/data/cve/CVE-2026-47514.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47511, CVE-2026-47512, CVE-2026-47513 | 7.8 | 0.0014 | | | [CVE-2026-47523](https://patchblox.com/security/data/cve/CVE-2026-47523.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47522, , CVE-2026-47524, CVE-2026-47525 | 7.8 | 0.0014 | | | [CVE-2026-47528](https://patchblox.com/security/data/cve/CVE-2026-47528.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47526, CVE-2026-47527, , CVE-2026-47529 | 7.8 | 0.0014 | | | [CVE-2026-47530](https://patchblox.com/security/data/cve/CVE-2026-47530.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47531, CVE-2026-47532, CVE-2026-47533 | 7.8 | 0.0014 | | | [CVE-2026-47540](https://patchblox.com/security/data/cve/CVE-2026-47540.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47534, CVE-2026-47537, CVE-2026-47538 | 7.8 | 0.0014 | | | [CVE-2026-47545](https://patchblox.com/security/data/cve/CVE-2026-47545.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47542, CVE-2026-47543, , CVE-2026-47546 | 7.8 | 0.0014 | | | [CVE-2026-47548](https://patchblox.com/security/data/cve/CVE-2026-47548.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47547, , CVE-2026-47549, CVE-2026-47551 | 7.8 | 0.0014 | | | [CVE-2026-47553](https://patchblox.com/security/data/cve/CVE-2026-47553.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47552, , CVE-2026-47554, CVE-2026-47555 | 7.8 | 0.0014 | | | [CVE-2026-47556](https://patchblox.com/security/data/cve/CVE-2026-47556.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47557, CVE-2026-47558, CVE-2026-47559 | 7.8 | 0.0014 | | | [CVE-2026-47558](https://patchblox.com/security/data/cve/CVE-2026-47558.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47556, CVE-2026-47557, , CVE-2026-47559 | 7.8 | 0.0014 | | | [CVE-2026-47561](https://patchblox.com/security/data/cve/CVE-2026-47561.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47560, , CVE-2026-47562, CVE-2026-47563 | 7.8 | 0.0014 | | | [CVE-2026-47563](https://patchblox.com/security/data/cve/CVE-2026-47563.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47560, CVE-2026-47561, CVE-2026-47562 | 7.8 | 0.0014 | | | [CVE-2026-47569](https://patchblox.com/security/data/cve/CVE-2026-47569.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47568, , CVE-2026-47572, CVE-2026-47586 | 7.8 | 0.0014 | | | [CVE-2026-47516](https://patchblox.com/security/data/cve/CVE-2026-47516.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47515, , CVE-2026-47517, CVE-2026-47518 | 7.8 | 0.0013 | | | [CVE-2026-47551](https://patchblox.com/security/data/cve/CVE-2026-47551.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47547, CVE-2026-47548, CVE-2026-47549 | 7.8 | 0.0013 | | | [CVE-2026-47560](https://patchblox.com/security/data/cve/CVE-2026-47560.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47561, CVE-2026-47562, CVE-2026-47563 | 7.8 | 0.0013 | | | [CVE-2026-47489](https://patchblox.com/security/data/cve/CVE-2026-47489.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47491, CVE-2026-47492, CVE-2026-47494 | 7.8 | 0.0013 | | | [CVE-2026-47552](https://patchblox.com/security/data/cve/CVE-2026-47552.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47553, CVE-2026-47554, CVE-2026-47555 | 7.8 | 0.0013 | | | [CVE-2026-47592](https://patchblox.com/security/data/cve/CVE-2026-47592.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47591, , CVE-2026-47594, CVE-2026-47595 | 7.8 | 0.0013 | | | [CVE-2026-47600](https://patchblox.com/security/data/cve/CVE-2026-47600.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47601, CVE-2026-47602, CVE-2026-47603 | 7.8 | 0.0013 | | | [CVE-2026-47587](https://patchblox.com/security/data/cve/CVE-2026-47587.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47588, CVE-2026-47589, CVE-2026-47590 | 7.8 | 0.0012 | | | [CVE-2026-47588](https://patchblox.com/security/data/cve/CVE-2026-47588.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47587, , CVE-2026-47589, CVE-2026-47590 | 7.8 | 0.0012 | | | [CVE-2026-47589](https://patchblox.com/security/data/cve/CVE-2026-47589.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47587, CVE-2026-47588, , CVE-2026-47590 | 7.8 | 0.0012 | | | [CVE-2026-47590](https://patchblox.com/security/data/cve/CVE-2026-47590.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47587, CVE-2026-47588, CVE-2026-47589 | 7.8 | 0.0012 | | | [CVE-2026-47594](https://patchblox.com/security/data/cve/CVE-2026-47594.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47591, CVE-2026-47592, , CVE-2026-47595 | 7.8 | 0.0012 | | | [CVE-2026-47559](https://patchblox.com/security/data/cve/CVE-2026-47559.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47556, CVE-2026-47557, CVE-2026-47558 | 7.8 | 0.0012 | | | [CVE-2026-47601](https://patchblox.com/security/data/cve/CVE-2026-47601.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47600, , CVE-2026-47602, CVE-2026-47603 | 7.8 | 0.0012 | | | [CVE-2026-47591](https://patchblox.com/security/data/cve/CVE-2026-47591.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47592, CVE-2026-47594, CVE-2026-47595 | 7.8 | 0.0012 | | | [CVE-2026-47595](https://patchblox.com/security/data/cve/CVE-2026-47595.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47591, CVE-2026-47592, CVE-2026-47594 | 7.8 | 0.0012 | | | [CVE-2026-47597](https://patchblox.com/security/data/cve/CVE-2026-47597.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47596, , CVE-2026-47598, CVE-2026-47599 | 7.8 | 0.0012 | | | [CVE-2026-47598](https://patchblox.com/security/data/cve/CVE-2026-47598.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47596, CVE-2026-47597, , CVE-2026-47599 | 7.0 | 0.0011 | | | [CVE-2026-47602](https://patchblox.com/security/data/cve/CVE-2026-47602.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47600, CVE-2026-47601, , CVE-2026-47603 | 7.1 | 0.0011 | | | [CVE-2026-47599](https://patchblox.com/security/data/cve/CVE-2026-47599.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47596, CVE-2026-47597, CVE-2026-47598 | 7.8 | 0.0011 | | | [CVE-2026-47554](https://patchblox.com/security/data/cve/CVE-2026-47554.md) | High | nvidia-open-driver-G07-signed: CVE-2026-47552, CVE-2026-47553, , CVE-2026-47555 | 7.1 | 0.0009 | | | [CVE-2026-47586](https://patchblox.com/security/data/cve/CVE-2026-47586.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47568, CVE-2026-47569, CVE-2026-47572 | 6.4 | 0.0018 | | | [CVE-2026-47502](https://patchblox.com/security/data/cve/CVE-2026-47502.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47500, CVE-2026-47501, , CVE-2026-47504 | n/a | 0.0015 | | | [CVE-2026-47509](https://patchblox.com/security/data/cve/CVE-2026-47509.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47507, CVE-2026-47508, , CVE-2026-47510 | 6.7 | 0.0014 | | | [CVE-2026-47515](https://patchblox.com/security/data/cve/CVE-2026-47515.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47516, CVE-2026-47517, CVE-2026-47518 | 6.7 | 0.0014 | | | [CVE-2026-47522](https://patchblox.com/security/data/cve/CVE-2026-47522.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47523, CVE-2026-47524, CVE-2026-47525 | 6.7 | 0.0014 | | | [CVE-2026-47524](https://patchblox.com/security/data/cve/CVE-2026-47524.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47522, CVE-2026-47523, , CVE-2026-47525 | 6.7 | 0.0014 | | | [CVE-2026-47525](https://patchblox.com/security/data/cve/CVE-2026-47525.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47522, CVE-2026-47523, CVE-2026-47524 | 6.7 | 0.0014 | | | [CVE-2026-47527](https://patchblox.com/security/data/cve/CVE-2026-47527.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47526, , CVE-2026-47528, CVE-2026-47529 | 6.7 | 0.0014 | | | [CVE-2026-47529](https://patchblox.com/security/data/cve/CVE-2026-47529.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47526, CVE-2026-47527, CVE-2026-47528 | 6.7 | 0.0014 | | | [CVE-2026-47532](https://patchblox.com/security/data/cve/CVE-2026-47532.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47530, CVE-2026-47531, , CVE-2026-47533 | 6.7 | 0.0014 | | | [CVE-2026-47533](https://patchblox.com/security/data/cve/CVE-2026-47533.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47530, CVE-2026-47531, CVE-2026-47532 | 6.7 | 0.0014 | | | [CVE-2026-47537](https://patchblox.com/security/data/cve/CVE-2026-47537.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47534, , CVE-2026-47538, CVE-2026-47540 | 6.7 | 0.0014 | | | [CVE-2026-47538](https://patchblox.com/security/data/cve/CVE-2026-47538.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47534, CVE-2026-47537, , CVE-2026-47540 | 6.7 | 0.0014 | | | [CVE-2026-47542](https://patchblox.com/security/data/cve/CVE-2026-47542.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47543, CVE-2026-47545, CVE-2026-47546 | 6.7 | 0.0014 | | | [CVE-2026-47543](https://patchblox.com/security/data/cve/CVE-2026-47543.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47542, , CVE-2026-47545, CVE-2026-47546 | 6.7 | 0.0014 | | | [CVE-2026-47546](https://patchblox.com/security/data/cve/CVE-2026-47546.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47542, CVE-2026-47543, CVE-2026-47545 | 6.7 | 0.0014 | | | [CVE-2026-47547](https://patchblox.com/security/data/cve/CVE-2026-47547.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47548, CVE-2026-47549, CVE-2026-47551 | 6.7 | 0.0014 | | | [CVE-2026-47572](https://patchblox.com/security/data/cve/CVE-2026-47572.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47568, CVE-2026-47569, , CVE-2026-47586 | n/a | 0.0014 | | | [CVE-2026-47555](https://patchblox.com/security/data/cve/CVE-2026-47555.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47552, CVE-2026-47553, CVE-2026-47554 | 5.5 | 0.0012 | | | [CVE-2026-47518](https://patchblox.com/security/data/cve/CVE-2026-47518.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47515, CVE-2026-47516, CVE-2026-47517 | 6.0 | 0.0012 | | | [CVE-2026-47534](https://patchblox.com/security/data/cve/CVE-2026-47534.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47537, CVE-2026-47538, CVE-2026-47540 | 5.5 | 0.0012 | | | [CVE-2026-47557](https://patchblox.com/security/data/cve/CVE-2026-47557.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47556, , CVE-2026-47558, CVE-2026-47559 | 5.5 | 0.0012 | | | [CVE-2026-47566](https://patchblox.com/security/data/cve/CVE-2026-47566.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47564, CVE-2026-47565, , CVE-2026-47567 | 5.5 | 0.0012 | | | [CVE-2026-47526](https://patchblox.com/security/data/cve/CVE-2026-47526.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47527, CVE-2026-47528, CVE-2026-47529 | 4.4 | 0.0012 | | | [CVE-2026-47531](https://patchblox.com/security/data/cve/CVE-2026-47531.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47530, , CVE-2026-47532, CVE-2026-47533 | 4.4 | 0.0012 | | | [CVE-2026-47517](https://patchblox.com/security/data/cve/CVE-2026-47517.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47515, CVE-2026-47516, , CVE-2026-47518 | 5.5 | 0.0012 | | | [CVE-2026-47549](https://patchblox.com/security/data/cve/CVE-2026-47549.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47547, CVE-2026-47548, , CVE-2026-47551 | 5.5 | 0.0012 | | | [CVE-2026-47567](https://patchblox.com/security/data/cve/CVE-2026-47567.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47564, CVE-2026-47565, CVE-2026-47566 | 5.5 | 0.0011 | | | [CVE-2026-47568](https://patchblox.com/security/data/cve/CVE-2026-47568.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47569, CVE-2026-47572, CVE-2026-47586 | 5.5 | 0.0011 | | | [CVE-2026-47492](https://patchblox.com/security/data/cve/CVE-2026-47492.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47489, CVE-2026-47491, , CVE-2026-47494 | 5.5 | 0.0011 | | | [CVE-2026-47562](https://patchblox.com/security/data/cve/CVE-2026-47562.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47560, CVE-2026-47561, , CVE-2026-47563 | 4.4 | 0.0011 | | | [CVE-2026-47565](https://patchblox.com/security/data/cve/CVE-2026-47565.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47564, , CVE-2026-47566, CVE-2026-47567 | 6.4 | 0.0010 | | | [CVE-2026-47603](https://patchblox.com/security/data/cve/CVE-2026-47603.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47600, CVE-2026-47601, CVE-2026-47602 | 5.5 | 0.0010 | | | [CVE-2026-47604](https://patchblox.com/security/data/cve/CVE-2026-47604.md) | Routine | nvidia-open-driver-G07-signed: Security update for nvidia-open-driver-G07-signed | 5.5 | 0.0010 | | | [CVE-2026-47564](https://patchblox.com/security/data/cve/CVE-2026-47564.md) | Routine | nvidia-open-driver-G07-signed: CVE-2026-47565, CVE-2026-47566, CVE-2026-47567 | n/a | n/a | | --- Data as of 2026-11-12T19:57:06Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.