{"url":"http://public2.vulnerablecode.io/api/packages/466544?format=json","purl":"pkg:apk/alpine/xen@4.17.2-r4?arch=riscv64&distroversion=edge&reponame=main","type":"apk","namespace":"alpine","name":"xen","version":"4.17.2-r4","qualifiers":{"arch":"riscv64","distroversion":"edge","reponame":"main"},"subpath":"","is_vulnerable":false,"next_non_vulnerable_version":"4.18.0-r2","latest_non_vulnerable_version":"4.21.1-r6","affected_by_vulnerabilities":[],"fixing_vulnerabilities":[{"url":"http://public2.vulnerablecode.io/api/vulnerabilities/106518?format=json","vulnerability_id":"VCID-fwx8-9f5e-v7hw","summary":"The current setup of the quarantine page tables assumes that the quarantine domain (dom_io) has been initialized with an address width of DEFAULT_DOMAIN_ADDRESS_WIDTH (48) and hence 4 page table levels.  However dom_io being a PV domain gets the AMD-Vi IOMMU page tables levels based on the maximum (hot pluggable) RAM address, and hence on systems with no RAM above the 512GB mark only 3 page-table levels are configured in the IOMMU.  On systems without RAM above the 512GB boundary amd_iommu_quarantine_init() will setup page tables for the scratch page with 4 levels, while the IOMMU will be configured to use 3 levels only, resulting in the last page table directory (PDE) effectively becoming a page table entry (PTE), and hence a device in quarantine mode gaining write access to the page destined to be a PDE.  Due to this page table level mismatch, the sink page the device gets read/write access to is no longer cleared between device assignment, possibly leading to data leaks.","references":[{"reference_url":"https://api.first.org/data/v1/epss?cve=CVE-2023-46835","reference_id":"","reference_type":"","scores":[{"value":"0.00087","scoring_system":"epss","scoring_elements":"0.24951","published_at":"2026-06-09T12:55:00Z"},{"value":"0.00087","scoring_system":"epss","scoring_elements":"0.25053","published_at":"2026-06-06T12:55:00Z"},{"value":"0.00087","scoring_system":"epss","scoring_elements":"0.25","published_at":"2026-06-07T12:55:00Z"},{"value":"0.00087","scoring_system":"epss","scoring_elements":"0.24943","published_at":"2026-06-08T12:55:00Z"},{"value":"0.00087","scoring_system":"epss","scoring_elements":"0.25065","published_at":"2026-06-05T12:55:00Z"}],"url":"https://api.first.org/data/v1/epss?cve=CVE-2023-46835"},{"reference_url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-46835","reference_id":"","reference_type":"","scores":[],"url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-46835"},{"reference_url":"https://ftp.suse.com/pub/projects/security/yaml/suse-cvss-scores.yaml","reference_id":"","reference_type":"","scores":[{"value":"6.5","scoring_system":"cvssv3.1","scoring_elements":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N"}],"url":"https://ftp.suse.com/pub/projects/security/yaml/suse-cvss-scores.yaml"},{"reference_url":"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056928","reference_id":"1056928","reference_type":"","scores":[],"url":"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056928"},{"reference_url":"https://xenbits.xenproject.org/xsa/advisory-445.html","reference_id":"advisory-445.html","reference_type":"","scores":[{"value":"5.5","scoring_system":"cvssv3.1","scoring_elements":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"},{"value":"Track","scoring_system":"ssvc","scoring_elements":"SSVCv2/E:N/A:N/T:P/P:M/B:A/M:M/D:T/2024-04-12T04:00:28Z/"}],"url":"https://xenbits.xenproject.org/xsa/advisory-445.html"},{"reference_url":"https://security.gentoo.org/glsa/202409-10","reference_id":"GLSA-202409-10","reference_type":"","scores":[],"url":"https://security.gentoo.org/glsa/202409-10"},{"reference_url":"https://xenbits.xen.org/xsa/advisory-445.html","reference_id":"XSA-445","reference_type":"","scores":[],"url":"https://xenbits.xen.org/xsa/advisory-445.html"}],"fixed_packages":[{"url":"http://public2.vulnerablecode.io/api/packages/466544?format=json","purl":"pkg:apk/alpine/xen@4.17.2-r4?arch=riscv64&distroversion=edge&reponame=main","is_vulnerable":false,"affected_by_vulnerabilities":[],"resource_url":"http://public2.vulnerablecode.io/packages/pkg:apk/alpine/xen@4.17.2-r4%3Farch=riscv64&distroversion=edge&reponame=main"}],"aliases":["CVE-2023-46835","XSA-445"],"risk_score":1.6,"exploitability":"0.5","weighted_severity":"3.2","resource_url":"http://public2.vulnerablecode.io/vulnerabilities/VCID-fwx8-9f5e-v7hw"},{"url":"http://public2.vulnerablecode.io/api/vulnerabilities/106519?format=json","vulnerability_id":"VCID-vkt6-fjzc-4uay","summary":"The fixes for XSA-422 (Branch Type Confusion) and XSA-434 (Speculative Return Stack Overflow) are not IRQ-safe.  It was believed that the mitigations always operated in contexts with IRQs disabled.  However, the original XSA-254 fix for Meltdown (XPTI) deliberately left interrupts enabled on two entry paths; one unconditionally, and one conditionally on whether XPTI was active.  As BTC/SRSO and Meltdown affect different CPU vendors, the mitigations are not active together by default.  Therefore, there is a race condition whereby a malicious PV guest can bypass BTC/SRSO protections and launch a BTC/SRSO attack against Xen.","references":[{"reference_url":"https://api.first.org/data/v1/epss?cve=CVE-2023-46836","reference_id":"","reference_type":"","scores":[{"value":"0.00021","scoring_system":"epss","scoring_elements":"0.06059","published_at":"2026-06-09T12:55:00Z"},{"value":"0.00021","scoring_system":"epss","scoring_elements":"0.06086","published_at":"2026-06-06T12:55:00Z"},{"value":"0.00021","scoring_system":"epss","scoring_elements":"0.06082","published_at":"2026-06-07T12:55:00Z"},{"value":"0.00021","scoring_system":"epss","scoring_elements":"0.06035","published_at":"2026-06-08T12:55:00Z"},{"value":"0.00021","scoring_system":"epss","scoring_elements":"0.06098","published_at":"2026-06-05T12:55:00Z"}],"url":"https://api.first.org/data/v1/epss?cve=CVE-2023-46836"},{"reference_url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-46836","reference_id":"","reference_type":"","scores":[],"url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-46836"},{"reference_url":"https://ftp.suse.com/pub/projects/security/yaml/suse-cvss-scores.yaml","reference_id":"","reference_type":"","scores":[{"value":"5.1","scoring_system":"cvssv3.1","scoring_elements":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N"}],"url":"https://ftp.suse.com/pub/projects/security/yaml/suse-cvss-scores.yaml"},{"reference_url":"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056928","reference_id":"1056928","reference_type":"","scores":[],"url":"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056928"},{"reference_url":"https://xenbits.xenproject.org/xsa/advisory-446.html","reference_id":"advisory-446.html","reference_type":"","scores":[{"value":"4.7","scoring_system":"cvssv3.1","scoring_elements":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N"},{"value":"Track","scoring_system":"ssvc","scoring_elements":"SSVCv2/E:N/A:N/T:P/P:M/B:A/M:M/D:T/2025-05-08T20:16:12Z/"}],"url":"https://xenbits.xenproject.org/xsa/advisory-446.html"},{"reference_url":"https://security.gentoo.org/glsa/202409-10","reference_id":"GLSA-202409-10","reference_type":"","scores":[],"url":"https://security.gentoo.org/glsa/202409-10"},{"reference_url":"https://xenbits.xen.org/xsa/advisory-446.html","reference_id":"XSA-446","reference_type":"","scores":[],"url":"https://xenbits.xen.org/xsa/advisory-446.html"}],"fixed_packages":[{"url":"http://public2.vulnerablecode.io/api/packages/466544?format=json","purl":"pkg:apk/alpine/xen@4.17.2-r4?arch=riscv64&distroversion=edge&reponame=main","is_vulnerable":false,"affected_by_vulnerabilities":[],"resource_url":"http://public2.vulnerablecode.io/packages/pkg:apk/alpine/xen@4.17.2-r4%3Farch=riscv64&distroversion=edge&reponame=main"}],"aliases":["CVE-2023-46836","XSA-446"],"risk_score":1.2,"exploitability":"0.5","weighted_severity":"2.5","resource_url":"http://public2.vulnerablecode.io/vulnerabilities/VCID-vkt6-fjzc-4uay"}],"risk_score":null,"resource_url":"http://public2.vulnerablecode.io/packages/pkg:apk/alpine/xen@4.17.2-r4%3Farch=riscv64&distroversion=edge&reponame=main"}