Jump to content

Welcome to ExtremeHW

Welcome to ExtremeHW, like most online communities you must register to view or post in our community, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of ExtremeHW by signing in or creating an account.

  • Start new topics and reply to others
  • Subscribe to topics and forums to get email updates
  • Get your own profile page and make new friends
  • Send personal messages to other members.
  • Take advantage of site exclusive features.
IGNORED

A security flaw leads Intel to disable DirectX 12 on its 4th Gen CPUs


ENTERPRISE
 Share

Recommended Posts

Quote

Intel has disabled DirectX 12 support on its 4th generation Haswell processors with onboard graphics due to a security vulnerability.  The vulnerability may allow escalation of privilege, or in other words, allow an unauthorized user to perform unwanted actions. 

It would seem to be a rather drastic action to disable DirectX 12 support completely, rather than issue an updated driver or patch, so it will be interesting to see if Intel makes further comment on the specifics of the vulnerability, or whether it has the potential to be exploited on other CPU generations.

Source 

 

Granted these are older CPU's, but a shame to lose a whole function. 

Link to comment
Share on other sites

Just now, UltraMega said:

This only affects the iGPU. Probably not a lot of people running dx12 on an old iGPU. 

 

Likely not indeed, so it is not what is considered a huge loss. Though yet another security hit for Intel. 

Link to comment
Share on other sites

37 minutes ago, ENTERPRISE said:

 

Likely not indeed, so it is not what is considered a huge loss. Though yet another security hit for Intel. 

Yea good point. Just to play devil's advocate though, can you really blame Intel for a security flaw in an API that came out way later than the hardware in question? 

Link to comment
Share on other sites

1 hour ago, UltraMega said:

Yea good point. Just to play devil's advocate though, can you really blame Intel for a security flaw in an API that came out way later than the hardware in question? 

That is true. Call it 50/50 blame lol.

  • Respect 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

This Website may place and access certain Cookies on your computer. ExtremeHW uses Cookies to improve your experience of using the Website and to improve our range of products and services. ExtremeHW has carefully chosen these Cookies and has taken steps to ensure that your privacy is protected and respected at all times. All Cookies used by this Website are used in accordance with current UK and EU Cookie Law. For more information please see our Privacy Policy