Malformed 32 byte TLS/SSL packet

I have the following packet when trying to examine an SSL session. This is a local capture but I have a capture from the target network as well. I see the same packet on both ends.

Frame 16: 540 bytes on wire (4320 bits), 540 bytes captured (4320 bits)
Internet Protocol Version 4, Src: 172.20.2.164 (172.20.2.164), Dst: 169.20.69.250 (169.20.69.250)
    Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00: Not-ECT (Not ECN-Capable Transport))
    Total Length: 526
    Flags: 0x02 (Don't Fragment)
    Header checksum: 0x790d [correct]
Transmission Control Protocol, Src Port: 57599 (57599), Dst Port: https (443), Seq: 2331060189, Ack: 18913651, Len: 474
Checksum: 0x56c7 [validation disabled]
Secure Sockets Layer
     TLSv1 Record Layer: Application Data Protocol: tcp
        Content Type: Application Data (23)
        Version: TLS 1.0 (0x0301)
        Length: 32
        Encrypted Application Data: 6a19a737cd1b4b0478dadd0a907f3b48fe6ba2b1c4a0bc6d...
    [Malformed Packet: TCP]
        Expert Info (Error/Malformed): Malformed Packet (Exception occurred)

IP's have been changed but the issue is the TLS record length. This is the packet being transmitted and received and the server is able to decrypt and process it correctly. The packet is what I believe to be the "GET" request. I just don't understand why the TLS length is so short. This is not part of a fragment. I am using the WireShark 1.6.2. Is this a problem with WireShark or the traffic? This is not a one off packet, my session contains multiple "malformed" 32 length TLS records, always from my client to the server.