fkie_cve-2025-7026
Vulnerability from fkie_nvd
Published
2025-07-11 16:15
Modified
2025-11-03 20:19
Severity ?
8.2 (High) - CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Summary
A vulnerability in the Software SMI handler (SwSmiInputValue 0xB2) allows a local attacker to control the RBX register, which is used as an unchecked pointer in the CommandRcx0 function. If the contents at RBX match certain expected values (e.g., '$DB$' or '2DB$'), the function performs arbitrary writes to System Management RAM (SMRAM), leading to potential privilege escalation to System Management Mode (SMM) and persistent firmware compromise.
References
cret@cert.orghttps://kb.cert.org/vuls/id/746790
cret@cert.orghttps://www.binarly.io/advisories/brly-dva-2025-008
cret@cert.orghttps://www.gigabyte.com/Support/Security
af854a3a-2127-422b-91ae-364da2661108https://www.kb.cert.org/vuls/id/746790
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "A vulnerability in the Software SMI handler (SwSmiInputValue 0xB2) allows a local attacker to control the RBX register, which is used as an unchecked pointer in the CommandRcx0 function. If the contents at RBX match certain expected values (e.g., \u0027$DB$\u0027 or \u00272DB$\u0027), the function performs arbitrary writes to System Management RAM (SMRAM), leading to potential privilege escalation to System Management Mode (SMM) and persistent firmware compromise."
    },
    {
      "lang": "es",
      "value": "Una vulnerabilidad en el controlador Software SMI (SwSmiInputValue 0xB2) permite a un atacante local controlar el registro RBX, que se utiliza como puntero sin control en la funci\u00f3n CommandRcx0. Si el contenido de RBX coincide con ciertos valores esperados (p. ej., \u0027$DB$\u0027 o \u00272DB$\u0027), la funci\u00f3n realiza escrituras arbitrarias en la RAM de administraci\u00f3n del sistema (SMRAM), lo que puede provocar una escalada de privilegios al modo de administraci\u00f3n del sistema (SMM) y una vulnerabilidad persistente del firmware."
    }
  ],
  "id": "CVE-2025-7026",
  "lastModified": "2025-11-03T20:19:20.127",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "LOCAL",
          "availabilityImpact": "HIGH",
          "baseScore": 8.2,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "HIGH",
          "scope": "CHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 1.5,
        "impactScore": 6.0,
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-07-11T16:15:26.897",
  "references": [
    {
      "source": "cret@cert.org",
      "url": "https://kb.cert.org/vuls/id/746790"
    },
    {
      "source": "cret@cert.org",
      "url": "https://www.binarly.io/advisories/brly-dva-2025-008"
    },
    {
      "source": "cret@cert.org",
      "url": "https://www.gigabyte.com/Support/Security"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "https://www.kb.cert.org/vuls/id/746790"
    }
  ],
  "sourceIdentifier": "cret@cert.org",
  "vulnStatus": "Awaiting Analysis"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.