[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f72Aj5qc9dMrGjc5HgmJNyC0M4UmPXiE17grFkenopG8":3,"g5a-risk:CVE-2023-4272":127},{"success":4,"data":5,"meta":124},true,{"cveId":6,"title":7,"description":8,"shortDescription":8,"publishedDate":9,"lastModified":10,"cvssScore":11,"cvssVector":12,"cvssMetrics":13,"epssScore":33,"epssPercentile":26,"epssTimeSeries":34,"severity":35,"affectedProducts":36,"affectedProductsCount":52,"references":53,"referencesCount":59,"weaknesses":60,"weaknessesCount":76,"isActivelyExploited":77,"cisaInfo":26,"otxData":26,"relatedBlogPosts":78,"seoMetadata":79,"configurations":104,"relatedVendorCves":122,"notableEvents":123},"CVE-2023-4272","What is CVE-2023-4272?","A local non-privileged user can make GPU processing operations that expose sensitive data from previously freed memory.","2023-11-07T16:15:29.25","2024-09-04T20:35:13.413",5.5,"CVSS:3.1\u002FAV:L\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N",{"CVSSMetricV31":14,"CVSSMetricV30":26,"CVSSMetricV2":26,"CVSSMetricV40":26},[15,29],{"Source":16,"Type":17,"CVSSData":18,"ExploitabilityScore":27,"ImpactScore":28},"nvd@nist.gov","Primary",{"Version":19,"VectorString":12,"AttackVector":20,"AttackComplexity":21,"PrivilegesRequired":21,"UserInteraction":22,"Scope":23,"ConfidentialityImpact":24,"IntegrityImpact":22,"AvailabilityImpact":22,"BaseScore":11,"BaseSeverity":25,"ExploitCodeMaturity":26,"RemediationLevel":26,"ReportConfidence":26,"TemporalScore":26,"TemporalSeverity":26,"ConfidentialityRequirement":26,"IntegrityRequirement":26,"AvailabilityRequirement":22,"ModifiedAttackVector":26,"ModifiedAttackComplexity":26,"ModifiedPrivilegesRequired":26,"ModifiedUserInteraction":26,"ModifiedScope":26,"ModifiedConfidentialityImpact":26,"ModifiedIntegrityImpact":26,"ModifiedAvailabilityImpact":26,"EnvironmentalScore":26,"EnvironmentalSeverity":26},"3.1","LOCAL","LOW","NONE","UNCHANGED","HIGH","MEDIUM",null,1.8,3.6,{"Source":30,"Type":31,"CVSSData":32,"ExploitabilityScore":27,"ImpactScore":28},"134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary",{"Version":19,"VectorString":12,"AttackVector":20,"AttackComplexity":21,"PrivilegesRequired":21,"UserInteraction":22,"Scope":23,"ConfidentialityImpact":24,"IntegrityImpact":22,"AvailabilityImpact":22,"BaseScore":11,"BaseSeverity":25,"ExploitCodeMaturity":26,"RemediationLevel":26,"ReportConfidence":26,"TemporalScore":26,"TemporalSeverity":26,"ConfidentialityRequirement":26,"IntegrityRequirement":26,"AvailabilityRequirement":22,"ModifiedAttackVector":26,"ModifiedAttackComplexity":26,"ModifiedPrivilegesRequired":26,"ModifiedUserInteraction":26,"ModifiedScope":26,"ModifiedConfidentialityImpact":26,"ModifiedIntegrityImpact":26,"ModifiedAvailabilityImpact":26,"EnvironmentalScore":26,"EnvironmentalSeverity":26},0.0034,[33,33,33,33,33,33,33],"Medium",[37,42,46,49],{"vendor":38,"product":39,"version":40,"criteria":41,"vulnerable":4},"arm","bifrost_gpu_kernel_driver","*","cpe:2.3:a:arm:bifrost_gpu_kernel_driver:*:*:*:*:*:*:*:*",{"vendor":38,"product":43,"version":44,"criteria":45,"vulnerable":4},"mali_gpu_kernel_driver","r41p0","cpe:2.3:a:arm:mali_gpu_kernel_driver:r41p0:*:*:*:*:*:*:*",{"vendor":38,"product":47,"version":40,"criteria":48,"vulnerable":4},"midgard_gpu_kernel_driver","cpe:2.3:a:arm:midgard_gpu_kernel_driver:*:*:*:*:*:*:*:*",{"vendor":38,"product":50,"version":40,"criteria":51,"vulnerable":4},"valhall_gpu_kernel_driver","cpe:2.3:a:arm:valhall_gpu_kernel_driver:*:*:*:*:*:*:*:*",4,[54],{"url":55,"source":56,"tags":57},"https:\u002F\u002Fdeveloper.arm.com\u002FArm%20Security%20Center\u002FMali%20GPU%20Driver%20Vulnerabilities","Arm",[58],"Vendor Advisory",1,[61,69],{"id":62,"name":63,"description":64,"extendedDescription":65,"status":66,"abstraction":67,"structure":68},"CWE-200","Exposure of Sensitive Information to an Unauthorized Actor","The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.","There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker.  Some kinds of sensitive information include:\nInformation might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected.  These parties include:\nInformation exposures can occur in different ways:\nIt is common practice to describe any loss of confidentiality as an \"information exposure,\" but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read.  CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.","Draft","Class","Simple",{"id":70,"name":71,"description":72,"extendedDescription":73,"status":74,"abstraction":75,"structure":68},"CWE-1251","Mirrored Regions with Different Values","The product's architecture mirrors regions without ensuring that their contents always stay in sync.","Having mirrored regions with different values might result in the exposure of sensitive information or possibly system compromise.\nIn the interest of increased performance, one might need to duplicate a resource. A cache memory is a common example of this concept, which keeps a \"local\" copy of a data element in the high speed cache memory. Unfortunately, this speed improvement comes with a downside, since the product needs to ensure that the local copy always mirrors the original copy truthfully. If they get out of sync, the computational result is no longer true.\nDuring hardware design, memory is not the only item which gets mirrored. There are many other entities that get mirrored, as well: registers, memory regions, and, in some cases, even whole computational units. For example, within a multi-core processor, if all memory accesses for each and every core goes through a single Memory-Management Unit (MMU) then the MMU will become a performance bottleneck. In such cases, duplicating local MMUs that will serve only a subset of the cores rather than all of them may resolve the performance issue. These local copies are also called \"shadow copies\" or \"mirrored copies.\"\nIf the original resource never changed, local duplicate copies getting out of sync would never be an issue. However, the values of the original copy will sometimes change. When the original copy changes, the mirrored copies must also change, and change fast.\nThis situation of shadow-copy-possibly-out-of-sync-with-original-copy might occur as a result of multiple scenarios, including the following:","Incomplete","Base",2,false,[],{"title":80,"metaDescription":81,"keywords":82,"canonicalUrl":83,"structuredData":84},"What is CVE-2023-4272? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2023-4272, a medium severity cyber security vulnerability from 2023. A local non-privileged user can make GPU processing operat...","CVE-2023-4272, CVE-2023-4272 vulnerability, CVE-2023-4272 security, medium severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2023, CVSS score, exploit, patch, remediation, arm security, bifrost_gpu_kernel_driver vulnerability, mali_gpu_kernel_driver vulnerability, midgard_gpu_kernel_driver vulnerability, valhall_gpu_kernel_driver vulnerability","\u002Fwhat-is\u002Fcve-2023-4272",{"@context":85,"@type":86,"headline":80,"description":81,"datePublished":9,"dateModified":10,"author":87,"publisher":91,"about":95,"mainEntityOfPage":99,"articleSection":102,"keywords":103},"https:\u002F\u002Fschema.org","TechArticle",{"@type":88,"name":89,"url":90},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":88,"name":89,"url":90,"logo":92},{"@type":93,"url":94},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":96,"name":6,"description":97,"additionalType":98},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":100,"@id":101},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2023-4272","Cybersecurity","CVE-2023-4272, CVE-2023-4272 vulnerability, CVE-2023-4272 security, medium severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[105],{"Operator":26,"Negate":26,"Nodes":106},[107],{"Operator":108,"Negate":26,"CPEMatch":109},"OR",[110,113,115,119],{"Vulnerable":4,"Criteria":41,"MatchCriteriaID":111,"VersionStartExcluding":26,"VersionStartIncluding":112,"VersionEndExcluding":26,"VersionEndIncluding":44},"711E2235-8C0F-4B8F-858F-E2EAAC124FA1","r0p0",{"Vulnerable":4,"Criteria":45,"MatchCriteriaID":114,"VersionStartExcluding":26,"VersionStartIncluding":26,"VersionEndExcluding":26,"VersionEndIncluding":26},"4B4EFDF6-BB81-48DF-BCC9-C22657E572AC",{"Vulnerable":4,"Criteria":48,"MatchCriteriaID":116,"VersionStartExcluding":26,"VersionStartIncluding":117,"VersionEndExcluding":26,"VersionEndIncluding":118},"1B466A44-0367-4F71-ABF0-CB031338B7E6","r8p0","r32p0",{"Vulnerable":4,"Criteria":51,"MatchCriteriaID":120,"VersionStartExcluding":26,"VersionStartIncluding":121,"VersionEndExcluding":26,"VersionEndIncluding":44},"2429D309-6700-447D-A068-F6F02DC6473B","r19p0",[],[],{"lastModified":10,"cacheTime":125,"version":126},1792269087935,"2.0",{"score":128,"band":129,"action":130,"scoredAt":131},18,"Info","Track","2026-10-16T06:59:45.63356+00:00"]